Table of contents
Downloading the Software
To install the ZMC, you must first download Amanda Enterprise Edition with the Zmanda Management Console. Packages for all Zmanda products are available from the Zmanda network downloads page. The Amanda Enterprise Edition with ZMC package includes:
- Amanda Enterprise Server
- Zmanda Client for the server
- The Zmanda Management Console
- all of the dependencies for Zmanda Management Console
Upgrading from earlier version of 3.3.x release
You can upgrade from earlier version of 3.3.x by running the installer. The installer detects the older version of 3.3.x release and automatically upgrade to newer release. Please check 3.3.x release notes for any caveats.
During upgrade, the installer will prompt the user to preserve configuration and catalog information. It is important to preserve configuration and catalog if you want to restore from older backup images and use backup set policies created using earlier version of 3.3.x release.
Installing Amanda Enterprise server on the Same Server as Zmanda Recovery Manager for MySQL 3.6 server
ZRM and Amanda Enterprise must be installed in a specific order to work. Please perform the following procedure as superuser on the backup server. If you need to install ZRM 3.6 on top of Amanda Enterprise 3.3.x, please contact Zmanda Support team.
- Install ZRM 3.6 server. Do NOT stop ZRM ZMC services at this stage.
- Install Amanda Enterprise 3.3.x server and Amanda Enterprise patches. Use different port from ZRM services for web server (both http and https ports) at the time of Amanda Enterprise server installation.
- Stop ZRM ZMC services
/etc/init.d/zmc_zrm stop
- Stop Amanda Enterprise ZMC services
/etc/init.d/zmc_aee stop
- Start ZRM ZMC services
/etc/init.d/zmc_zrm start
- Start Amanda Enterprise ZMC services
/etc/init.d/zmc_aee start
Acquiring and Installing License file
After you have purchased a base license and any feature licenses (such as application module licenses), the Zmanda Network Downloads page will include an option to download a license key (zmanda_license). Download this file and save the file as /etc/zmanda/zmanda_license on the Amanda Enterprise server, then make sure that the file permissions are set to 644 and owner is root.
Secure Socket Layer (SSL) Certification
Although the Zmanda Management Console 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 Zmanda 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.
The ZMC Rapid Installer
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 (it may have .bin extension also) is executable. For example:
# chmod +x amanda-enterprise-3.3.2-installer.run
4. Run the installer by double-clicking on it, or enter the following command line:
# ./amanda-enterprise-3.3.2-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 Amanda Enterprise binaries have been extracted and installed, the Zmanda Management Console is launched and the readme file is displayed. The readme file includes the default Zmanda Management Console username and password. You can now login to the console using any supported browser and begin configuring backup sets.
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), xwindow, text, or unattended. The unattended mode allows users to install the product without user interaction in an automated manner.
--debugtrace debugtracefile - Installer debug logs will be in debugtracefile. This option is not required for installation.
- --installer-language installer-language
- Choose installer language. This is not supported by Zmanda installer. Only en (English) is supported.
- --apache_server_port apache_server_port
- The ZMC Web Server port (default is 80).
- --apache_server_ssl_port apache_server_ssl_port
- ZMC Web Server SSL port (default is 443).
- --mysql_port mysql_port
- Specify the ZMC MySQL Server port (default is 3037).
Uninstalling Amanda Enterprise
Important Note to Customers of ZRM for MySQL: Before running the uninstall script for Amanda Enterprise, you must first stop the ZRM for MySQL services from running (enter /etc/init.d/zmc_zrm_init stop as root), then restart it manually after the uninstall script completes (/etc/init.d/zmc_zrm_init start).
You can uninstall Amanda Enterprise by running the uninstall script located at /opt/zmanda/amanda/uninstall on the backup server. Using this script, you can remove the Amanda Enterprise binaries, with the option of leaving configuration files intact. Follow the on-screen instructions after running the script.
The uninstaller program does not remove the backup scheduled in the crontab. They will have to be removed manually.
Accessing Zmanda Management Console
Zmanda Management Console is accessed using a web browser. Amanda Enterprise is supported on latest version of Internet Explorer, Mozilla FireFox and Google Chrome.
Please access https://<host name of the Amanda server>/ if you are using default port. If you had changed the port number using installation, please use URL https://<host name of the Amanda server>:<port number>/
The default port is 443. Please make sure access to this port is allowed by network configuration (such as firewalls).