LogoLogo
EBR DocsHelp
Zmanda Pro
Zmanda Pro
  • Welcome to the Zmanda Pro Documentation
  • Overview and Concepts​
  • Best Practices
  • Start Here
    • Initial Security Setup
    • Step 1: Adding a User
    • Step 2: Client Download and Installation
    • Step 3: Client Login
    • Step 4: Adding a New Storage Vault
    • Step 5: Adding a New Protected Item
    • Step 6: Initiating a Backup
    • Step 7: Checking Backup Job Status
    • Step 8: Restore Data
  • Guide
    • Zmanda Pro Server Deployment (On-prem)
      • Zmanda Pro Self-Hosted Deployment
        • Self-Hosted Online Server
        • Self-Hosted Online Server Setup
        • Self-Hosted Offline Server
        • Self-Hosted Offline Server Setup
        • Storage Manager Service
        • Storage Manager Service Setup
        • Zmanda Pro Client Setup
        • Disaster Recovery Plan: Self-Hosted Server
        • Disaster Recovery Plan: Self-Hosted Server Recovery Workflow
        • Admin Password Reset
        • Custom Certificates Upload
    • Zmanda Pro Usage
    • Zmanda Pro Client Installation
      • Zmanda Pro user configuration
      • Storage configuration
    • Restarting at boot ​(Linux)
    • Protected Items
      • Files and Folders
      • MySQL
        • Xtrabackup
          • Configuration
          • Backup
          • Restore
          • Recover
        • MyDumper
          • Configuration
          • Backup
          • Restore
          • Recover
        • MySQLDump
          • Configuration
          • Backup
          • Restore
          • Recover
        • LVM
          • Configuration
          • Backup
          • Restore
          • Recover
        • Managing Data Directory Permissions with SELinux and AppArmor
        • Compatibility Matrix
      • MariaDB
        • MariaBackup
          • Configuration
          • Backup
          • Restore
          • Recover
        • MyDumper
          • Configuration
          • Backup
          • Restore
          • Recover
        • MariaDBDump
          • Configuration
          • Backup
          • Restore
          • Recover
        • LVM
          • Configuration
          • Backup
          • Restore
          • Recover
        • Managing Data Directory Permissions with SELinux and AppArmor
        • Compatibility Matrix
      • Microsoft Office 365
      • Postgres
      • Program Output
      • Microsoft Hyper-V
      • Microsoft SQL Server
      • MongoDB
      • Windows Server System State
      • Application-Aware Writer
      • Disk Image
      • VMware vSphere
        • Configuration
        • Backup
        • Restore
        • Troubleshooting
      • MariaDB
        • Backup & Restore MariaDB with a staging path
        • Backup & Restore MariaDB without a staging path using Streaming
      • Oracle RMAN
        • Configuration
        • Backup
        • Restore
        • Perform a Full Database Backup with Oracle RMAN
        • Perform a database backup using a Custom Oracle RMAN Script
        • Restore an Oracle RMAN backup using Backup Manager
        • Recover an Oracle database after restoring from Zmanda Pro Backup Manager
        • Troubleshooting Oracle RMAN backups with Backup Manager
    • Configure SSO
    • Configure & Apply Policies
    • Configure Email Reporting
    • Backup Manager
      • Login
    • Automation Tools
      • Bulk Operations with ZPAT
        • Bulk addition of policies
        • Bulk onboarding of devices
        • Bulk deletion of users
        • Bulk Rename of Devices
        • Bulk Restore
        • Bulk addition of protected items
        • Bulk administration of client devices with Ansible
      • Disaster Recovery Plan: Zmanda Pro Clients
    • Encryption & Key Management
    • Zmanda Pro Job Statuses
    • Disk Image Walkthrough
      • Create & Use Recovery Media
    • Common Problems & Solutions
    • Troubleshooting
    • VMware to Hyper-V Migration
      • Configuration
      • Backup
      • Restore to Hyper-V
Powered by GitBook
LogoLogo

Quick Links

  • Amanda Community Wiki
  • Amanda Community Downloads
  • Share Feedback

About

  • About Us
  • Customer Testimonials

Terms

  • Terms of Use
  • Privacy Policy

Contact Info

  • Denver, CO, USA
  • 888-496-2632 (US)
  • 408-732-3208 (INT)

2025 © Zmanda, A BETSOL Company

On this page
  • Prerequisites
  • Configuration Process
  • Protected Item Configuration Menu
  • Selecting a Protected Item Configuration
  • Configuration Options

Was this helpful?

Export as PDF
  1. Guide
  2. Protected Items
  3. MariaDB
  4. MariaBackup

Configuration

Prerequisites

MariaDB Database Configuration

Linux:

Install and configure MariaDB database

Start and enable MariaDB service

# Start the service
systemctl start mariadb
# Enable the service
systemctl enable mariadb

MariaDB User creation

We recommend you to create a separate mariadb user with the following grants- BACKUP_ADMIN, PROCESS, RELOAD, LOCK TABLES, REPLICATION CLIENT

CREATE USER '<username>'@'localhost' IDENTIFIED BY '<password>';
GRANT BACKUP_ADMIN, PROCESS, RELOAD, LOCK TABLES, REPLICATION CLIENT,BINLOG MONITOR, SUPER, SLAVE MONITOR
  ON *.* TO 'bkpuser'@'localhost';
GRANT SELECT ON performance_schema.log_status TO 'bkpuser'@'localhost';
GRANT SELECT ON performance_schema.keyring_component_status TO bkpuser@'localhost';
GRANT SELECT ON performance_schema.replication_group_members TO bkpuser@'localhost';
FLUSH PRIVILEGES;

Zmanda Pro client installed and registered.

Backupmanager installed and login configured.

Configuration Process

Start the MySQL configuration

  1. Open your terminal and run the following command to begin the MySQL configuration process:

    backupmanager mysql configure

  2. When prompted, enter the Device Name as registered on the server. The default value will be the hostname of the client machine you are configuring.

Note: Pressing the Delete key will exit from backupmanager.

Protected Item Configuration Menu

Once the device name is entered, you'll see the Protected Item configuration menu with the following options:

  • Edit Protected Item: Modify an existing Protected Item configuration.

  • Add Protected Item: Set up a new Protected Item configuration.

  • Exit: Exit the configuration process (this will exit backupmanager).

To create or modify a backup, choose either Edit Protected Item or Add Protected Item.

Selecting a Protected Item Configuration

When editing an existing protected item, you will be presented with a list of previously configured items.

  • Use the arrow keys to navigate through the list of protected items.

  • Details of the active selection (Name and ID) will be displayed below for verification.

  • You can select an item by pressing Enter.

Example:

  • [Back]: Returns to the previous menu.

  • [List of protected items]: Displays all available source configurations for the logged-in user.

Configuration Options

Once a protected item is selected, you'll be able to configure the following settings:

  1. Database information These details are required for connecting to the MySQL server during backup and recovery.

    1. First-Time Setup If you are configuring authentication for the first time, you’ll need to provide the following details:

      1. Database Username: The backup username to access the MySQL server.

      2. Database Password: The corresponding password.

      3. Hostname: The hostname or IP address of the MySQL server

      4. Database Port: The port on which the MySQL server is running (3306 is the default)

      5. Database Socket File Path: The path to the socket file used for connecting to the MySQL server

      6. Data Directory: The path to directory where MySQL stores its databases, tables and other crucial files.

      7. Binary Log Directory: The path to directory where MySQL stores its binary logs.

      8. Configuration File Path: The path to the primary configuration file where MySQL’s settings are defined.

      9. Database Version: The MySQL server version (Fetched automatically)

      10. Binary Log Format: The format in which changes to the MySQL server are recorded in the binary log (Fetched automatically). In case binary logging is not enabled on the server, it is preferred to have the binary logs configured to one of the following options:

        1. Row format

        2. Mixed format

    2. Existing Authentication

      If authentication has already been set up, you’ll see the following options:

      1. View Database Configuration: View current database connection details.

      2. Edit Database Configuration: Modify existing credentials.

  2. Test Connection: Test if the provided credentials can successfully connect to the MySQL server.

  3. Backup Information This step offers a range of options to configure your backup according to your strategy and specific requirements. You can customize settings such as the backup tool, method, scope, level, and more, ensuring your backup process aligns precisely with your needs.

    1. Backup Tool Name: Specify the tool for performing backups; in this case, select XtraBackup.

    2. Backup Method: Choose between XtraBackup Raw or Streaming backups. Compatibility Check: XtraBackup and MySQL server versions will be validated for compatibility automatically—no user input is required here.

    3. Parallel Thread Count: Configure the number of threads that will be spawned during backup and recovery in XtraBackup to optimize performance.

    4. Backup Scope: Select whether to back up all databases, specific databases, or individual tables within a particular database.

    5. Backup Level: Choose the backup level: Full or Incremental.

      1. Full: This will backup the selected backup scope in its current state for each backup run.

      2. Incremental (Chained differential): This will capture and backup the changes from the previous backup run.

  4. Staging Information In this stage, set up paths for data and binary log staging before they are transferred to Zmanda Pro.

    1. Data Staging Path: Enter the path where XtraBackup stores its backups temporarily before transferring them to Zmanda Pro.

    2. Binary Log Staging Path: Specify the location where MySQL server binary logs are stored temporarily before being backed up to Zmanda Pro.

  5. Purging behavior of binary logs Decide if you would like to purge binary logs after each backup:

    1. Yes - All the binary logs that were backed up in the previous backup run will be purged after the current backup run is completed.

    2. No

  6. Storage information In this section, specify where backup information will be stored:

    1. Backup Destination: Select a storage destination to store the backup inventory and details.

  7. Saving the Configuration Once all the configurations are completed, make sure to save your changes. Select Save from the main configuration menu to ensure your settings are applied.

  8. Exiting the Configuration After saving your changes, you can exit the backupmanager utility by selecting Exit from the main menu. Be sure to save your work before exiting.

When modifying the storage vault in the storage information section, it's crucial to understand that this change will be applied to all existing scripts configured.

You can gracefully exit the backupmanager at any point during the process by pressing "Ctrl+C".

PreviousMariaBackupNextBackup

Last updated 2 months ago

Was this helpful?