Project:Zmanda Recovery Manager for MySQL 3.5 > ZRM Enterprise Edition 3.5 Release Notes

ZRM Enterprise Edition 3.5 Release Notes

ZRM Enterprise 3.5 provides new functionality and has fixes for the issues reported by ZRM Enterprise customers (see the changes below). 

Compatibility with previous versions of ZRM Enterprise

  • ZRM Enterprise 3.5 Installer detects the existing installation of ZRM Enterprise 3.4.  Users can upgrade  from ZRM Enterprise 3.4 release automatically. Please save the configuration when prompted during the upgrade process.
  • It will be necessary to upgrade ZRM clients to 3.5 if you plan to use new backup method such as streaming backups using Xtrabackup, MySQL Enterprise backup.

Upgrading to ZRM Enterprise 3.5

You can upgrade from ZRM server from 3.4 to 3.5 by running the ZRM server 3.5 installer. It will automatically detect the presence of earlier installation and prompt the user for the upgrade. The configuration will be preserved during upgrade. Before the upgrade process, it is important to make a copy of /etc/mysql-zrm/mysql-zrm.conf* files on the ZRM server. If there are changes to this file, they will have to manually merged. Please contact Zmanda support if you need help with the merge.

You can upgrade the ZRM client software on the clients by running package install program such as rpm, dpkg, pkgadd as appropriate for the platform. If the package manager does not provide an upgrade option, you can uninstall 3.4 package and install 3.5 package.

Users upgrading from releases earlier than ZRM 3.4 should contact Zmanda Support team. Zmanda offers Quick Upgrade services for customers who would like Zmanda to perform the upgrade from older releases.

Note: If you are planning to upgrading by uninstalling the 3.4 version and installing ZRM Enterprise 3.5, you must make a copy of /etc/mysql-zrm/mysql-zrm.conf* files on the ZRM server. Otherwise, the changes to these files will be lost (Site specific backup set configuration).

Compatibility with Amanda Enterprise

The Amanda backup server can reside on the same machine as the ZRM server.  Amanda Enteprise 3.3.x is compatible with ZRM server 3.5.  Please use the following procedure (order of steps is important):

  • Install Amanda 3.3.x or ZRM 3.5 server (i.e. install the first product if it is not installed)
  • Change permissions on /etc/zmanda directory on the backup server

# chmod 777 /etc/zmanda

  • Change permissions on the configuration files

# chmod 755 /etc/zmanda/*.cnf

  • Install ZRM 3.5/Amanda 3.3.x server (install the other product)
  • Change permissions on the configuration files that were installed in the last step

# chmod 755 /etc/zmanda/*.cnf

  • Restart the ZMC services in the following order

# /etc/init.d/zmc_aee stop

# /etc/init.d/zmc_zrm stop

# /etc/init.d/zmc_zrm start

# /etc/init.d/zmc_aee start

  • You should be able to configure Amanda and ZRM backup sets using ZMC

For installing ZRM 3.5 along with older versions of Amanda Enterprise, please contact Zmanda Support team before installation.


  • Support for newer versions of Xtrabackup and MySQL Enterprise Backup.
  • Streaming backups from MySQL server. Requires less disk space on the MySQL server.
  • Global reports across all backup sets in the Zmanda Management Console.
  • ZMC enhancements such as tool tips for various input fields, auto-completion for backup set names in backup set switcher.
  • Restores to replication slave can be controlled - you can restore only or relay logs or all replication files.
  • Quick (no-copy) backups can be restored to another MySQL server.
  • A critical bug in restoration of incremental backups has been fixed. The incremental backup restoration used to failed with "Duplicate event" MySQL error.
  • ZRM 3.4.1 and 3.4.2 patch fixes are rolled into the 3.5 release.


For a full list of supported platforms please review the compatibility guide here.

ZRM Enterprise 3.5 documentation provides detailed information on how to install and configure Amanda server and client on these platforms.

Known Issues

  • Restoration of streaming backup of empty database performed using xtrabackup is marked as an restoration error. All other databases are restored.
  • Network disruption during MySQL backup from a Windows server might cause the backup status not to be updated. The user will have to abort the backup in the ZMC manually.