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

ZRM Enterprise Edition 3.3 Release Notes

ZRM Enterprise 3.3 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.3 Rapid Installer detects the existing installation of ZRM Enterprise 3.2.  Users can upgrade  from ZRM Enterprise 3.2 release automatically. Please save the configuration when prompted during the upgrade process.
  • The default copy plugin has been changed to socket in ZRM 3.3 and default full backup method has been changed to logical backups in ZRM 3.3. Customers should check their backup sets if they are using correct values after upgrade.
  • In ZRM 3.3, 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.
  • ZRM 3.2 Windows clients will work with ZRM 3.3 Linux/Solaris server and ZRM 3.1 Windows server.

Upgrading to ZRM Enterprise 3.3

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

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

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

New Features

  • ZRM Enterprise server and client support for Ubuntu 11.04, Fedora 14 and Debian 6
  • Support for Xtrabackup - Block based Differential and Incremental Backups.
  • Support for table restoration from a database backup.

Customer reported issues that have fixed

  • Pre-Scheduler plugin scheduling delays are handled correctly.
  • Scheduled incremental backups work.
  • Backup How compression and on the fly compression settings are handled.
  • Logs are not flushed twice in snapshot full backup method.
  • Email address in ZMC Set site defaults can be saved.
  • Issues with backup retention policy and Quick snapshots are fixed.
  • Snapshot backups of databases with hyphen in the name are handled.
  • Database/Table sizes are computed on demand instead of automatically and improving Backup What page load performance.
  • All ZRM 3.2 patches are also merged into 3.3

Known Issues

  • Click OK button in ZMC About page after reviewing version information. All other operations cannot be performed.
  • When Xtrabackup 1.7 is available and you are using Xtrabackup tool for backups, please upgrade to the newer version.

Documentation

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

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