ZRM Enterprise 3.9 provides new functionality and has fixes for the issues reported by ZRM Enterprise customers (see the changes below). There is no 3.9 Windows server or client release. ZRM Enterprise 3.9 server works with ZRM Windows Client 3.7.
Compatibility with Previous Versions of ZRM Enterprise
Upgrading to ZRM Enterprise 3.9
You can upgrade from ZRM server from 3.8 to 3.9 by running the ZRM server 3.9 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.
Users upgrading from ZRM Enterprise 3.8 and earlier should be aware of following changes:
1. After upgrading to ZRM 3.9, please clear browser cache before accessing Zmanda Management Console. Otherwise, cached components from ZRM 3.8 might appear in the browser.
2. If you are performing table level restores of backups done using earlier releases of ZRM, you will have to run following command as mysql user on the ZRM server
$ /usr/bin/mysql-zrm-parse-sql --source-directory <backup image directory>
--update-table-list
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.8 package and install 3.9 package.
Note: If you are planning to upgrade by uninstalling the 3.8 version and installing ZRM Enterprise 3.9, 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.9. Please use the following procedure (order of steps is important):
Changes