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
      • Microsoft Exchange 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
  • Recovery
  • Prerequisites
  • Steps to Recover

Was this helpful?

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

Recover

Recovery

The below documentation provides a detailed step-by-step process for recovering MySQL workload backups using Zmanda Pro's backupmanager.

Prerequisites

  • Successful restore of the selected snapshot and its associated snapshots is required to perform recovery

Steps to Recover

  1. Initiate the Recovery Command To start the recovery process, execute the following command on the client machine:

    # MariaDB Workload
    backupmanager mariadb recover --pi-name <Protected Item Name>
  2. Select Recovery Type Choose between a full recovery or full and incremental recovery. For Point-In-Time Recovery (PITR), select the incremental recovery option.

    a. Full Recovery

    • If you select a full recovery, the process will restore your server, database, or table to the point of the latest full backup

    b. Incremental Recovery

    • If incremental recovery is chosen, you'll be prompted to select either an incremental recovery or a point-in-time recovery

      1. Incremental Recovery: Restores data to the point of the selected incremental backup

      2. Point-In-Time Recovery (PITR): You will be prompted to select a time range from the available snapshots

Point-In-Time Recovery Steps

  1. Select a time range:

    Start: 2024-10-29 10:59:09, End: 2024-10-29 11:00:23
    Start: 2024-10-29 08:40:57, End: 2024-10-29 10:59:08
    Exit
  2. Select a Binary Log After selecting a time range, choose a specific binary log file within that time frame for recovery. Example:

    binlog.000284
    Start: 2024-10-29 10:59:09
    End: 2024-10-29 11:00:23
    [BACK]
  3. Select a Commit Once a binary log is chosen, you can specify the particular commit for restoration based on the queries and timestamps listed. Example:

    Select from queries
    [BACK]
    
    Select preferred time stamp?
    [BACK]
    ▸ Commit 1 2024 11:00:02
    Commit 2 2024 11:00:04
    
    --------- Commit Details ----------
    Query 1
    INSERT INTO new.`my_table` SET @1=13 @2='incall'
    Timestamp: 2024-10-29 11:00:02
  4. Initiate Recovery After selecting the desired timestamp, the recovery process will begin. Once completed, the output will confirm the success of the full and PITR recovery.

    Proceeding with PITR Recovery...
    Starting recovery flow
    Full recovery binlog_file_name: binlog.000284
    Full recovery binlog_file_position: 158
    Full binlog and PITR binlog applied successfully
    Recovery flow completed successfully
    Updating status file as the restore and recovery flow is complete

This process ensures precise control over your MariaDB data recovery, allowing you to restore data accurately to the desired point in time.

PreviousRestoreNextLVM

Last updated 5 months ago

Was this helpful?