Download License and Binaries

Download License File

You can download your trial/production license file from Zmanda Network. 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.   

Steps to download the license file: 

STEP 1: Login to your Zmanda network account and click the download icon for the license you wish to download

STEP 2: Enter the MAC address of your ZMC server and a name. Once the details are entered, click on submit and license downloads successfully.  If there is any change in MAC and server name then Customer can contact the sales team or support team

11 1.09L15 11.43l-1.108-1.089c-1.822-1.788-4.802-1.788-6.622 0l-2.905 2.852a4.558 4.558 0 00.357 6.82c1.893 1.517 4.695 1.226 6.422-.47"/> </g><Secure Socket Layer (SSL) Certification  

ZMC is shipped with a pre-packaged Apache SSL certificate. We recommend you to purchase external CA certified SSL certificates or create your own self-signed SSL certificates and distribute to all browsers/clients from which you wish to access the ZMC portal. The pre-packaged SSL certificates may generate warnings on some browser versions. 

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.    

Steps for generating self-signed certificates: 

We need to generate two self-singed certificates, one for zmc-service and another for ae-service. We are using openssl for generating certificates. 

1.   

      1. To generate the key and certificate for zmc_service 

a)    openssl req -newkey rsa:2048 -nodes -keyout zmanda-zmc.key -x509 -days 365 -out zmanda-zmc.crt 

b)    Copy the generated files ('zmanda-zmc' .key & .crt) to the directory "/var/lib/amanda/". There would be two hidden files ‘.self-signed.key' and '.self-signed.crt' in this directory ('ls -lart' will show the hidden files).  

c)    Rename the zmanda-zmc.key and zmanda-zmc.crt files to '.self-signed.key' and '.self-signed.crt' respectively.  

2. To generate the key and certificate for ae_service 

a)    openssl req -newkey rsa:2048 -nodes -keyout zmanda-aee.key -x509 -days 365 -out zmanda-aee.crt 

b)    Copy the generated files ('zmanda-aee' .key & .crt) to the directory "/var/lib/amanda/". There would be two hidden files '.tlsv3_aee.key' and '.tlsv3_aee.crt' in this directory ('ls -lart' will show the hidden files).  

c)    Rename the zmanda-aee.key and zmanda-aee.crt files self-generated to '.tlsv3_aee.key' and '.tlsv3_aee.crt' respectively. 

3. Now restart the zmc and ae services by executing the following commands  

a)        systemctl restart run-zmanda-backup-server.service 

b)        systemctl restart run-zmanda-zmc.service