To install the ZMC, you must first download Zmanda Backup Server and Zmanda Management Console. Packages for all Zmanda products are available from the Zmanda network downloads page.  

The Zmanda Backup Server package includes:  

·                       Zmanda Enterprise Server  

·                       Shared dependencies for both packages.  

  

The Zmanda Management Console package includes:  

  

·                       The Zmanda Management Console  

·                       Shared dependencies for both packages.  

  

Upgrading from Earlier Version of 3.6 Release to 4.1 

Please refer to this link Migration page.  

Acquiring and Installing the License File  

After you have purchased a base license and any feature licenses (such as application module licenses), the Zmanda Network Home page will include an option to download a license key (zmanda_license), after you bind the license to the MAC address of the machine on which the Zmanda Management Console will be installed. Download license file and upload it on the Zmanda Management Console in the “Licenses” section, under the “Settings” tab. For more details please the License page.  

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 zmanda-zmc-installer-x64.run    

  # chmod +x zmanda-backup-server-installer-x64.run   

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

  # ./ zmanda-backup-server-installer-x64.run   

  # ./ zmanda-zmc-installer-x64.run   

5. The Rapid Installer then starts. Follow the on-screen instructions.  

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 Zmanda binaries have been extracted and installed, the link will be displayed to launch Zmanda Management Console 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.  

Uninstalling Amanda Enterprise  

You can uninstall Zmanda Management Console and Zmanda Backup Server by running the uninstall script located at /opt/zmanda/amanda/zmanda-zmc-pkg/uninstall and /opt/zmanda/amanda/zmanda-backup-pkg/uninstall respectively. Using this script, you can remove the Zmanda 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.  

 

 

Note : Before upgrading to 4.0.0.1 please follow below instructions for clean uninstallation of 4.0 :  

For Debian based  systems use :    

  # apt-get remove -y zmanda-platform-shared

For RPM based  systems use :  

  # dnf remove -y zmanda-platform-shared                                    [ OR ]

  # yum remove -y zmanda-platform-shared

 

Accessing Zmanda Management Console  

Zmanda Management Console is accessed using a web browser. Zmanda Management Console is supported on latest version of Google Chrome, Mozilla FireFox, Internet Explorer and Microsoft edge.  

Please access https://<host name of the Zmanda rest server>:8008/ if you are using the default port. If you had changed the port number using installation, please use URL https://<host name of the Zmanda rest server>:<port number>/.  

The default port is 8008. Please make sure access to this port is allowed by network configuration (such as firewalls).