This MindTouch Deki has expired; please contact your system administrator. Visit MindTouch.com for activation information.

Download

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 Linux or Solaris Client for the server
  • The Zmanda Management Console
  • all of the dependencies for Zmanda Management Console.

Note that browser access to the ZMC requires IE 6 or greater on Windows and Firefox 3.0 or greater on Windows, Linux and Mac OS X. Other browsers may work, but are not exhaustively tested.

If you are installing Amanda Enterprise 3.0 on the same machine as a Zmanda Recovery Manager for MySQL server, you must restart the ZRM processes as described here. 

Upgrading from Amanda enterprise 2.6.4

To upgrade from Amanda enterprise version 2.6.4, you must uninstall the old installation and run the version 3.0 installer. Uninstalling the old release while saving the configuration files is the only way to preserve the backup sets you created in the old release; Amanda Enterprise 3.0 cannot directly process backup sets created in older versions of the product. This upgrade procedure only migrates backup set configurations created with the Zmanda Management Console. If you have manually edited Amanda configuration files that need to be preserved, please contact the Zmanda Support Team for assistance.

  1. Begin by backing up all configuration information by running the zm-support tool as described here. Copy the resulting tarball to a safe location.
  2. Uninstall 2.6.4 by running /opt/zmanda/amanda/uninstall and answering "yes" to the "save old data set" prompt. Important Note for customers running ZRM for MySQL and Amanda on the same server: 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 stop as root), then restart it manually after the uninstall script completes (/etc/init.d/zmc_zrm start).
  3. Run the downloaded 3.0 installer. It will detect existing installation data and ask for confirmation to copy data from the previous installation.

If you exit the upgrade by clicking No, the installer exits without changing the current installation. If you click Yes to continue with the upgrade, the installer proceeds with the upgrade after you have accepted the License Agreement and have been warned about installing a non-supported distribution.

Caution: Canceling or otherwise interrupting this upgrade process can disable a
working Zmanda Management Console installation. Subsequent attempts to access
the ZMC will then return "cannot reach the localhost" messages. If you
interrupt the upgrade for any reason, make sure to restart the upgrade and run
it to completion.

You are also given the option to retain existing log files, which we recommend that you keep. If the existing files are overwritten, the ZMC will re-fetch Alerts received from Zmanda Network even though the User may have already seen them.

After installation,

  1. You should clear the cache on the browser you use to access the ZMC after completing the upgrade.
  2. When you login, you will be in Admin|Backup Sets page. It will show the status of backup sets that have been migrated to 3.0. Only backup set configuration files that have been migrated to 3.0 will be available for use. Please use Migrate link to migrate backup sets. See Amanda Enterprise 3.0 release notes for more information.

 

Upgrading Amanda Enterprise 2.6.4 (32-bit) clients to Amanda Enterprise 3.0 (64-bit)

You must uninstall the 2.6.4 32-bit client before installing the 3.0 64-bit version. Uninstalling the 2.6.4 32-bit version is only required if you are upgrading to the 64-bit version of Amanda Enterprise 3.0 client software.

Installing Amanda Enterprise on the Same Server as Zmanda Recovery Manager for MySQL

After you have used the Rapid Installer (see below) to successfully install Amanda Enterprise 3.0, there are two additional steps to make such an installation work:

  1. Become root and enter the following command at the operating system prompt:
         /etc/init.d/zmc_zrm restart
  2. Still as root, run the following commands and examine the output to make sure that all services are up and running:
        /etc/init.d/zmc_zrm status
       /etc/init.d/zmc_aee status

 

Acquiring and Installing License Keys

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 to the /etc/zmanda directory 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.0-installer.bin 

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

  #  ./amanda-enterprise-3.0-installer.bin

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.

Powered by MindTouch Deki v.8.08.2