Download distribution files from from the Zmanda Network Downloads page. Note that there are a number of different packages for various MySQL server and ZRM server architectures.
If you are installing ZRM for MySQL version 3.4 over a previous version, please see the "Compatibility with Previous Versions of the Zmanda Recovery Manager for MySQL" section of the ZRM for MySQL 3.5 Release Notes.
The ZRM Server is the backup server. It can run either Linux, Solaris, or Windows. The installer.run (or, for Windows, installer-win.exe) packages are binary executables for the ZMC Rapid Installer, which install the ZRM Server software, the Zmanda Management Console (ZMC) and all dependencies: this is the recommended method of installation. The installer.run packages include the ZRM command line interface and ZRM client software. The installation instructions are provided in the next section.
The MySQL server is the machine being backed up (i.e., the backup client). No ZRM client components are required if logical backup and recovery of MySQL server.
# rpm -i MySQL-zrm-enterprise-client-3.5-1.noarch.rpm
# dpkg -i mysql-zrm-enterprise-client_3.5_all.deb
# pkgadd -G -d .
For installation using a method other than the Rapid Installer, please see the sections that follow.
1. Copy the Rapid Installer binary file to the host where the given component will be installed.
2. Log in to the host as the superuser.
3. Make sure that the Rapid Installer binary file is executable. For example:
# chmod +x ZRM-enterprise-3.5-installer.run
4. Run the installer by double-clicking on it, or enter the following command line:
# ./ZRM-enterprise-3.5-installer.run
5. The Rapid Installer then starts. Follow the on-screen instructions.
Important Note: When prompted to choose the Zmanda Web Server protocol, we strongly recommend that you choose https for security reasons. Even if you choose http for browser/ZMC communication, the ZMC still requires HTTPS for internal communication purposes, and will therefore prompt you for an SSL port during installation in all cases.
Note: The installer performs several tasks after creating and populating the Zmanda directories. These are completed after the progress bar (which only tracks the archive extraction) shows 100% completion. These tasks take time. Please wait till they complete.
6. After the ZRM for MySQL binaries have been extracted and installed, the Zmanda Management Console is launched and the readme file is displayed. The readme file includes the default ZRM for MySQL username and password. You can now login to the console using any supported browser and begin backing up MySQL databases.
7. After installing the ZRM server, please make sure license keys are installed on the ZRM server.
Run the installer with the --help option to see what command line parameters are available.
Important Note to Customers of Amanda Enterprise Edition: Before running the uninstall script for ZRM for MySQL, you must first stop the Amanda Enterprise Edition services from running (enter /etc/init.d/zmc stop as root), then restart it manually after the uninstall script completes (/etc/init.d/zmc start).
You can unistall ZRM for MySQL by clicking the uninstall script located in /opt/zmanda/zrm/uninstall. Using this script, you can remove the ZRM for MySQL binaries, with the option of leaving configuration files intact. Follow the on-screen instructions after running the script.
Installation must be run from the Administrator account. First, make sure that system meets the requirements for ZRM servers on Windows. If the correct version of ActivePerl is not installed (5.8.8) before installing ZRM for MySQL server, the ZRM installation program will prompt you to install it before it will allow you to continue. If you do not have access to this version of Perl, please contact Zmanda Support Team.
The installer performs several tasks after creating and populating the Zmanda directories. These are completed after the progress bar (which only tracks the archive extraction) shows 100% completion. These tasks take time. Please wait until they complete.
After the server and client software has been extracted and installed, the Zmanda Management Console is launched and the readme file is displayed. The readme file includes the default ZRM for MySQL username and password. You can now login to the console using any supported browser and begin backing up MySQL databases.
The following services are installed as part of ZRM for MySQL server, and must be running for the ZRM server to function:
After installing the ZRM server, please make sure license file is installed on the ZRM server.
You can use the Uninstall ZRM option added to the Windows Start->All Programs menu or the Add/Remove Programs option from the Control Panel to remove ZRM for MySQL from the system. After you initiate the uninstall, you are prompted whether you would like to remove backup configuration data as well as the program itself. If you plan to upgrade, you should choose to keep the configuration data.
Note that removing the ZRM Windows Client requires that you use the Add/Remove Programs option available on the Windows Control Panel.
After you have purchased a base license and any feature licenses (such as a snapshot license), the Zmanda Network Downloads page will include an option to download a license file (zmanda_license). On Linux/Solaris ZRM servers, download the license file to the /etc/zmanda directory, then make sure that the file permissions are set to 644 and that the owner is root. On Windows ZRM servers, download the file to ZRM_installation_dir\etc\zmanda as the Administrator.
Although ZRM for MySQL is shipped with pre-packaged Apache SSL certificate to get you started, Zmanda recommends you purchase (or create your own self-signed) SSL certificates and distribute them to all the browsers from which you wish to access the ZMC. The pre-packaged certificates are not secure (as they are shared by all ZRM for MySQL customers). These generic certificates will also generate security warnings on some browser versions.
Zmanda recommends that you either 1) Create self-signed certificates and distribute them to all the client machines that require access to the ZMC, or 2) Distribute certificates from a recognized Certificate Authority. Option 1 (self-signed certificates) is free, and is adequate for most organizations that deploy ZMC servers and the machines that access them behind the same firewall.
If using a certificate from a recognized Certificate Authority, your browser will automatically create the secure connection with no errors or warnings.
If using a self-signed certificate, you must then deploy a mechanism to get the relevant browser(s) to accept this new root CA. One method is to generate the certificate using a special format that can be directly imported by common web browsers, and then providing a link on a secure intranet for ZMC users to download (web browsers automatically display the import dialog if the file is in the correct format and sent by the intranet web server using the correct mimetype). PKCS12 (now part of OpenSSL, provides a mechanism to distribute self-signed private key certificates in a number formats recognized by different browsers.
Another approach is to manually add the new self-signed root CA to the root CA list of the client system, which will automatically provide access to the new CA for all web browsers on the client system. This article covers the procedures for doing this in a Microsoft Windows server environment.
For more details on certificate validation issues, see this article from OpenSSL.