Zmanda skillfully integrates various MariaDB incremental backups and full backups using MariaDB Binary Logs. This downright enables you to take very frequent backups as well as do a point-in-time restore using any backup image.

The Zmanda Recovery Manager (ZRM) smart scheduler starts all backup processes. Depending on the MySQL server, storage engine, and underlying storage technology (for example, whether snapshots are available), ZRM intelligently decides what kind of backup to perform. The primary consideration is impact on the database.

If snapshot fails because there is not enough space in the reserved area, ZRM performs a logical backup. It is always possible to override ZRM’s recommendations. For example, instead of using a snapshot you can force ZRM to perform a logical backup. ZRM will index all backups to track the metadata required for a successful restore. Every day ZRM checks if any backups are older than the retention policy (the number of days or months that backups should be kept). The expired backups are purged from the ZRM backup index and removed from the disk. A reporting engine provides customizable reports in either text or HTML format. For ZRM installed on Linux or Solaris reports can be distributed by e-mail or by RSS feed. For ZRM installed on Windows all backup information is logged in a Windows event log. With ZRM, place your recovery first to make it last.

Choosing Logical non-parallel option uses a mysqldump backup that copies MySQL binary logs regardless of the storage engine. MySQL binary logs track and save all database server transactions as a list of SQL statements. To implement a logical backup strategy, binary logging must be enabled on the MySQL server, and a path to the log files must be supplied (the default is /var/lib/mysql) in the Binary Log Path field.

Logical backup method works with all MySQL storage engines except the MySQL cluster NDB storage engine. Logical backups can also be restored to any platform architecture or database that supports SQL. For example: Backups of MySQL database running on Redhat Enterprise server powerpc platform can be restored to Ubuntu server running on x86 platform.

Because logical backups require a read lock on the database(s) or tables being backed up  (not in the case all tables are using InnoDB storage engine), they can have a greater impact on the applications using the MySQL database. Logical backups also result in increased restore times, as restoring the data is accomplished by re-playing the transactions against the target database instead of just copying files. In case of InnoDB tables, the backups are performed as a single transaction and will not obtain any locks.

MariaDB provides a consistent, ACID-compliant scaling solution for enterprises with requirements that can’t be met with other alternatives like replication and sharding.

Distributed SQL provides scalability, and MariaDB provides the flexibility to choose how much scalability you need.

Managing backups of 1 Production DB or a strong clusters of 100’s, Zamanda Recovery Manager offers a seamless onboarding process for new MariaDB databases, while ensuring robust reliability for existing databases.

 Yes, Zmanda production support team is available 24 x 7 over both phone and email. You can choose our Standard or Premium level of support, made available to you with complete knowledge base access, email and phone support, case management, software enhancements and security updates. Please visit- contact support to get in touch with our support team.

To enable IT to test Zmanda on demo environments - we offer a fully licensed version of Zmanda for 14 days. Please fill out our Free Trial form, and our sales team will help you get started.