Project:Zmanda Recovery Manager for MySQL 3.3 > ZRM Enterprise 3.3.2 Release Notes
Table of contents
ZRM Enterprise 3.3.2 is a minor release that add support for MariaDB and provides bug fixes for ZRM 3.3 release. This release includes changes for both ZRM server and client.
All 3.3 customers are recommended to install this release. This release replaces ZRM 3.3.1 release.
It is important to read ZRM 3.3 release notes and ZRM Enterprise 3.3 documentation also.
Installation procedure
Note: Zmanda Management Console should not be in use during this process. ZRM backup or restoration should not be in progress. Customers should have installed ZRM 3.3 on both ZRM server and MySQL server before installing ZRM 3.3.2.
- ZRM Enterprise 3.3.2 should be installed on ZRM server and client (MySQL server)
- Copy the release tar ball as super user on the ZRM server/client.
- Extract the tar ball in a temporary directory.
# gunzip patch-ZRM-3.3.2.tar.gz
- Change permissions for the installation script in the patch-ZRM-3.3.2 sub-directory.
# chmod 700 patch.sh
- Run the script
# ./patch.sh
Changes in the release
- Support for MariaDB and SkySQL Enterprise MySQL servers. XtraBackup 1.6 release must be used.
- Failures to clean up after snapshot full backups are treated as warnings.
- Fixes to ZMC backup reporting page to make sure all backup runs are reported.
- Handle copy plugin failures better and better logging of failures.
- Amazon EBS snapshot error reporting has been improved.
- Fixes to Xtrabackup backup failures in MySQL server 5.5.
- Pre-scheduler plugin removes the old scheduled entries.
- Ability to perform full logical backups (no incremental backups) without enabling binary logs in replication configurations. Please add --master-data=2 to the Logical Backup Options in backup set's Backup How page if you want the master information in the binary logs.