Download

Downloading ZRM for MySQL & MariaDB Packages

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 & MariaDB version 3.9 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.9 Release Notes.

 

ZRM Linux Dependencies

Refer the table below and install the respective dependencies based on the operating system before installing ZRM for MySQL & MariaDB binaries.

 

Operating system  

Versions  

Dependencies Required  

  

  

  

  

  

 Ubuntu  

  

  

16.04, 18.04  

sudo apt-get install -y libc6-i386 lib32stdc++6 lib32gcc1 lib32z1  

18.10 

  

sudo apt-get install -y libc6-i386 lib32stdc++6 lib32gcc1  lib32z1 libxml-parser-perl cron  

20.04  

sudo apt update  

sudo apt-get install -y libc6-i386 lib32stdc++6 lib32gcc1  lib32z1 libxml-parser-perl cron libcrypt1:i386  

 

RHEL/Centos  

6, 7, 8  

yum install -y glibc.i686 libgcc.i686 libstdc++.i686 ncurses-libs.i686 zlib.i686 libcrypt.so.1  

 

Oracle Enterprise Linux 

6, 7, 8 

yum install -y glibc.i686 libgcc.i686 libstdc++.i686 ncurses-libs.i686 zlib.i686 libcrypt.so.1 

 

 

 

Fedora 

28, 29 

dnf install -y glibc.i686 libgcc.i686 libstdc++.i686  zlib.i686 libxcrypt.i686 libnsl.i686 ncurses-compat-libs.i686 

30, 31 

dnf install -y glibc.i686 libgcc.i686 libstdc++.i686  zlib.i686 libnsl.i686 libxcrypt-compat.i686 cronie xinetd ncurses-compat-libs.i686 

 

Debian 

9, 10 

sudo apt-get install -y libc6-i386 lib32stdc++6 lib32gcc1  lib32z1 libxml-parser-perl 

 

 

SUSE Linux 

12 

zypper install  glibc.i686 libgcc.i686 libstdc++.i686 ncurses-libs.i686 zlib.i686 libcrypt.so.1 

15 

zypper install glibc-32bit libgcc_s1-32bit libstdc++6-32bit libncurses5-32bit libz1-32bit libcrypto43-32bit 

 

OpenSUSE 

15 

zypper install  glibc-32bit libgcc_s1-32bit libstdc++6-32bit libncurses5-32bit libz1-32bit libcrypto43-32bit 

ZRM Server Components

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. Theinstaller.run packages include the ZRM command line interface and ZRM client software. The installation instructions are provided in the next section.

Linux

ZRM-enterprise-3.9-installer.run  
All supported linux distributions.

Solaris

ZRM-enterprise-3.4-installer-sparc.run
Solaris on Sparc platform
ZRM-enterprise-3.4-installer-intel.run
Solaris on Intel/AMD platform

Windows

ZRM-enterprise-3.1-installer-win.exe 
Windows on x86 (32bit only)

MySQL Server (ZRM client) Components

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.

Linux

 
MySQL-zrm-enterprise-client-3.9-1.noarch.rpm 
RHEL, SLES and Fedora distribution. Install using the following command (run as root):
# rpm -i MySQL-zrm-enterprise-client-3.9-1.noarch.rpm
mysql-zrm-enterprise-client_3.9_all.deb 
Ubuntu, Debian distribution. Install using the following command (run as root):
# dpkg -i mysql-zrm-enterprise-client_3.9_all.deb

 

Solaris

MySQL-zrm-client-3.9-solaris.pkg 
Open Solaris and Solaris 10 on Intel/AMD and Sparc platforms. After downloading the Solaris client package, install using the following command (run as superuser) in the directory where the package was downloaded :
# pkgadd -G -d .
The above command installs the package in all zones.

 

Windows

ZRM-Windows-*.zip 
Windows 32bit and 64bit platforms. Latest version of Windows client is 3.7. Install by extracting the archive and running the resulting Setup.exe. Administrator privileges are required for installation.
During installation, you have to specify the name of ZRM server or its IP address. If this information is not available at the time of ZRM client installation, You can use ZRM client configuration utility (Start > Programs > ZRM Client For MySQL > ZRM Client Configuration Utility > Server) to set the correct IP address of ZRM server and restart ZWC Service from the Services menu. ZRM client must be registered with ZRM server before backups are performed.

The ZMC Rapid Installer (Linux and Unix)

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.9-installer.run

4. Run the installer by double-clicking on it, or enter the following command line:

  #  ./ZRM-enterprise-3.9-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 & MariaDB 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 & MariaDB username and password. You can now login to the console using any supported browser and begin backing up MySQL & MariaDB databases.

7. After installing the ZRM server, please make sure license keys are installed on the ZRM server.

 

Rapid Installer Command Line Options

Run the installer with the --help option to see what command line parameters are available.

--help 
Display the list of valid options.
--version 
Display product version information.
--optionfile optionfile 
Use command line parameters specified in optionfile.
--mode mode 
Choose the installation mode, where mode is gtk (the default), xwindowtext, or unattended.
--apache_server_port apache_server_port 
The ZMC Web Server port (default is 80).
--apache_server_ssl_port apache_server_sslport 
ZMC Web Server SSL port (default is 443).
--mysql_port mysql_port 
Specify the ZMC MySQL Server port (default is 3036).

 

Uninstalling ZRM for MySQL & MariaDB (Linux and UNIX)

Important Note to Customers of Amanda Enterprise Edition: Before running the uninstall script for ZRM for MySQL & MariaDB, 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 & MariaDB binaries, with the option of leaving configuration files intact. Follow the on-screen instructions after running the script.

 

The ZMC Rapid Installer (Windows)

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 & MariaDB 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.

  1. Obtain the Windows ZRM server installation program ZRM-enterprise-3.1-installer-win.exe from the Zmanda Network Downloads page. Go to the folder where you downloaded the file and double-click it to start the installation. Stay connected to the internet during the installation process. Installing some of the dependencies requires internet access.
  2. Follow the on-screen instructions. Because the installation program installs the Zmanda Windows Client as well as the web server and ZRM server, it must extract a large number of files before the setup process can begin. Please be patient.
  3. 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.

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 & MariaDB username and password. You can now login to the console using any supported browser and begin backing up MySQL & MariaDB databases.

The following services are installed as part of ZRM for MySQL & MariaDB server, and must be running for the ZRM server to function:

  • ZMC Service
  • ZRM Enterprise Apache
  • ZRM Enterprise MySQL
  • ZWC service

 After installing the ZRM server, please make sure license file is installed on the ZRM server.

Uninstalling ZRM for MySQL & MariaDB Windows Server

You can use the Uninstall ZRM option added to the Windows Start->All Programs menu or the Add/Remove Programsoption from the Control Panel to remove ZRM for MySQL & MariaDB 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.

Installing ZRM License

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.

Secure Socket Layer (SSL) Certificate for ZMC web server

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 & MariaDB 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.