ZRM Enterprise Edition 3.2 Release Notes

Compatibility with previous versions of ZRM Enterprise

• ZRM Enterprise 3.2 Rapid Installer detects the existing installation of ZRM Enterprise 3.1.  Users can upgrade only from ZRM Enterprise 3.1 release. Please save the configuration when prompted during the upgrade process.
• Upgrade ZRM clients to 3.2 before upgrading the ZRM Enterprise server to 3.2
• In ZRM 3.2 (compared to earlier releases), full backups include MySQL server binary logs. If the binary log configuration in the ZMC is not complete and binary logs are enabled in the MySQL server, full backups will have warning messages. The backups are present in the catalog and can be restored. Selective recovery between last incremental backup and full backup will not work.

Upgrading to ZRM Enterprise 3.2

You can upgrade from ZRM server from 3.1 to 3.2 by running the ZRM server 3.2 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.1 package and install 3.2 package.

Users upgrading from releases earlier than 3.1 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.1 version and installing ZRM Enterprise 3.2, 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.1.3 is compatible with ZRM server 3.2.  Please use the following procedure (order of steps is important):

• Install Amanda 3.1.3 or ZRM 3.2 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.2/Amanda 3.1.3 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.2 along with older versions of Amanda Enterprise, please contact Zmanda Support team before installation.

New Features

• ZRM Enterprise server and client support for RedHat Enterprise 6, Ubuntu 10.10, Ubuntu 10.04, Ubuntu 9.10, Debian 5.0, Fedora 11 and Fedora 12 has been added.
• Support of MySQL Enterprise Backup - Block based Differential and Incremental Backups.
• Improved logging and error reporting.
• Binary logs are backed up as part of full backups. This allows user to perform selective restoration between last incremental backup and full backup.
• ZMC enhancements
  • Monitor Events page monitors and manages events across backup sets.
  • Licenses and Services pages to track ZRM license usage and ZRM service status.
  • Customize logical backups by providing mysqldump options in the Backup How Page.
  • Changing log verbosity in Backup How page.
  • Backup What page shows database and table sizes. This allows users to estimate the size of backup set and provision backup storage.
  • Backup Summary page performs enhanced configuration checks on the ZRM server as well as the MySQL server.
  • Ability to gracefully abort running backups and restores. Cancel button in the Monitor Backup page for backup runs and in the Restore/Convert backup pages.
• ZRM notification emails include the URL for Zmanda Management Console.

Customer reported issues that have fixed

• Scheduled backups fail abruptly and no message is logged in the ZMC.
• Binary logging is turned off during incremental backup restoration. This avoids duplication of events in future incremental backups.
• The number of rows in ZMC tables can be selected.
• ZMC Backup What page can handle thousands of tables and databases without resulting in web page timeouts.
• ZMC Login process does not fail when there are lots of ZMC backup and restore events.

Known Issues

• Click OK button in ZMC About page after reviewing version information. All other operations cannot be performed.

Documentation

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

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