Project:Zmanda Recovery Manager for MySQL 3.7 > ZRM Enterprise 3.7.2 Release Notes
Table of contents
ZRM Enterprise 3.7.2 provides bug fixes for ZRM 3.7 release. This release includes changes to ZRM server and ZRM client. It also rolls up fixes from ZRM 3.7.1 patch release.
All 3.7 customers are recommended to install this release.
It is important to read ZRM 3.7 release notes and ZRM Enterprise 3.7 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.7 on both ZRM server and MySQL server before installing ZRM 3.7.2
- ZRM Enterprise 3.7.2 should be installed on ZRM server and ZRM client.
- Copy the downloaded patch tar ball as super user to the ZRM server or ZRM client (where MySQL server is running)
- Extract the tar ball in a temporary directory as superuser.
# tar xzf patch-ZRM-3.7.2.tar.gz
- Change directory to patch-ZRM-3.7.2 sub-directory.
- Change permissions for the installation script.
# chmod 700 patch.pl
- Run the script as superuser.
# ./patch.pl
Changes in the release
- Some backup set names were not displayed in the ZMC backup set selector. This issue has been fixed.
- ZRM backups will fail if backup process is not able to flush database logs to the disk.
- Xtrabackup backups do not get stuck trying to read a temporary file(s) created during the backup.
- ZMC Backup When interface was confusing when a new schedule is defined. The usability of schedule creation has been improved.
- Restoration to MySQL 5.6 servers do not fail with this patch.
- Support for MySQL Enterprise Backup 3.10.x
- Support for Ubuntu 14.04 and all distributions using Gnu tar 1.27 version.