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
  • Pre-requisites
  • Restores Triggered from the Client machine
  • Restores Triggered from the Server-UI

Was this helpful?

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

Restore

The following outlines the step-by-step process for restoring MariaDB workload backups using Zmanda Pro's backupmanager.

Pre-requisites

  1. Make sure Backup Manager login command is run and configurations are loaded before starting with restore.

  2. Ensure Zmanda Pro is installed and properly configured on the client machine.

  3. Backup Manager must be installed on the client machine.

  4. You must know the Protected Item (PI) name and the Storage Information name used for backups.

  5. The device on which you are running the restore must be connected to the Zmanda Pro server on which the chosen protected backups exists.

Restores Triggered from the Client machine

If the restore command is exited (either gracefully or forcefully), the inventory may not close properly. As a workaround, you'll need to manually delete all inventory related files after exiting the restore process.

1. Initiate the Restore Command

On the client machine, execute the following command in the terminal:

# MariaDB Workload
backupmanager mariadb restore --pi-name <Protected Item Name>

2. Select the snapshot

You will be prompted to select the snapshot you wish to restore. For Point-In-Time Recovery, choose an incremental snapshot to restore data to a specific point-in-time.

Example:

Use the arrow keys to navigate: ↓ ↑ → ←
 Select the snapshot you wish to restore to. For Point-In-Time Recovery, select an Incremental snapshot:
▸ 2024-10-29 15:24:09 incremental - (Captured MariaDB data between 2024-10-29 11:23:01 UTC and 2024-10-29 11:24:02 UTC)
  2024-10-29 15:23:13 full - (Captured MariaDB data between 2024-10-28 14:10:41 UTC and 2024-10-29 11:23:01 UTC)

3. Snapshot Restoration Process

Upon selecting a snapshot, the necessary snapshots will automatically begin restoring.

Example:

Selected Snapshot: 2024-10-29 15:24:09 incremental
(Captured MariaDB data between 2024-10-29 11:23:01 UTC and 2024-10-29 11:24:02 UTC)
Restoring snapshots... \         
Enqueued task : MariaDB restore snapshot 63060
Enqueued task : MariaDB restore snapshot 3515e
Enqueued task : MariaDB restore snapshot 63533
Initiating restore task for snapshotID: 63060
Initiating restore task for snapshotID: 3515e
Initiating restore task for snapshotID: 63533
Restoring snapshots... |          
Completed restore of snapshot : 3515e
Restoring snapshots... /          
Completed restore of snapshot : 63533
Completed restore of snapshot : 63060
Restoring snapshots...... Done!

You can choose to proceed with the recovery immediately by selecting "Yes" at the prompt or defer it to a later time according to your needs.

Restores Triggered from the Server-UI

Follow these steps to schedule and initiate a restore from the Zmanda Pro Server-UI

  1. Log onto Zmanda Pro Web Portal

    • Access the Zmanda Pro web portal using your user credentials.

  2. Navigate to the Restore Menu

    • Click on the "Restore" section to proceed with the restore process.

  3. Restore Process

    1. Select the client device and the storage vault from which you want to restore.

    2. Click Next to proceed.

    3. Choose the primary protected item you wish to restore, then select View All to display available snapshots.

    4. Pick the snapshot you want to restore and click Next to proceed to the final configuration step.

    5. Choose Program Input option in the "Restore As" field.

    6. Enter the following command in the "command" field:

      # MariaDB Workload
      /usr/local/bin/backupmanager mariadb restore --pi-name <Protected-Item-Name> --program-input
    7. From the "Process multiple files using:" field, choose the Archive option and select *tar from the dropdown menu.

    8. Click Restore to begin the process.

PreviousBackupNextRecover

Last updated 4 months ago

Was this helpful?