Table of contents
ZRM Enterprise 3.6.1 provides bug fixes for ZRM 3.6 release. This release includes changes for both ZRM server and client.
All 3.6 customers are recommended to install this release.
It is important to read ZRM 3.6 release notes and ZRM Enterprise 3.6 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.6 on both ZRM server and MySQL server before installing ZRM 3.6.1
- ZRM Enterprise 3.6.1 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 as superuser.
# gunzip patch-ZRM-3.6.1.tar.gz
- Change permissions for the installation script in the patch-ZRM-3.6.1 sub-directory.
# chmod 700 patch.pl
- Run the script as superuser.
# ./patch.pl
Changes in the release
- ZRM backups continue when MySQL Enterprise Backup prints a warning message.
- Table level restores work for compressed backups
- Selective restoration of databases/tables is possible for MySQL server 5.6
- Backup errors are displayed in Monitor pages and Report Summary pages
- Backup images are purged as retention policy even if the backup images are stored as symbolic links to some other location
- Binary logs are not flushed if Copy Binary Logs are disabled for full backups
- Backup encryption works with both gpg2 and gpg