Zmanda Backup Server Appliance is a Vmware Virtual Machine with Amanda Enterprise 3.6 server images, patches and dependencies. It includes both Amanda server and client packages. All Amanda pre-requisites to perform file system backups to disk are installed. Additional packages might be required for backups of other applications/databases. Please go through Zmanda Application documentation for details.
Server backup virtual appliance uses 64bit CentOS 7 and Ubuntu 16.04 distributions.
Appliance Images
The appliance image is available in OVF (.ova) format. This image works on VMware ESX 4.x and ESX 5.x
Disk space requirements: The appliance performs backups to disk. It expects about 130GB for disk space in the Vmware data store to perform backups. The minimum disk space requirement is 250GB.
How to Use These Images
- Download the images from Zmanda Network to the machine where Vmware vSphere or vCenter console is running.
- Importing Backup appliance image into Vmware
- Vmware ESX 4.x or 5.x : To impor t .ova file, In the vSphere Client, select File-> Deploy OVF Template. Specify the source location in Deploy from a File or URL . Select the host where you want to deploy the ZBA. Select the datastore for the ZBA virtual machine. Select the disk format as Thin Provisioned. Click Finish, to import the ZBA. Click on Power on the virtual machine to boot the virtual machine from the vSphere Client panel.
- Free version of VMware : Please use VMware ovftool. Please see OVF Tool User Guide for instructions to import OVF files.
Backup Server Configuration
- When the virtual machine has booted up, you will be connected to the Zmanda Management Console to manage the backup set configuration.
- The root password for the virtual machine is zmanda. Please change the password before deploying it in production.
- The host name of the virtual machine is zmanda-aee-36, and it will obtain an IP address using dhcp. Please make sure zmanda-aee-36 is added to the name server or resolvable using /etc/hosts file.
- Access https://<ip address of this virtual machine>:443/ from Firefox or Internet Explorer to connect to the Zmanda Management Console (ZMC) running on the virtual machine.
- There is a demo-set backup set configured to backup Zmanda appliance's /etc directory to disk virtual tapes (under /var/lib/amanda directory). The backups will run daily and has retention policy of 7 days. The data disk of 125 GB is mounted at /var/lib/amanda directory. VMware backups use /var/lib/amanda/tmp as the temporary directory for backups.
- Please download and install the Amanda Enterprise license file from Zmanda Network (Click Downloads tab after logging into Zmanda Network). The license file has to be installed on the Virtual machine as /etc/zmanda/zmanda_license for the Zmanda Management Console to work.
- The Virtual machine is ready for backup set configuration and running backups using ZMC. Please see Zmanda Management Console Users Manual for more information.
- To set the timezone correctly use Set Timezone option in the Virtual machine console.
- To perform VMware backups on the Virtual Appliance, you will have to install VMware VCLI package from VMware. You will need VCLI 5.1 or higher version. Please set http_proxy and ftp_proxy to "" before running VCLI installer, if ZBA has direct access to internet. Otherwise, you will have to set these variables to point to the proxy server.
Configuring Tape Drives and Changer
The default backup set is configured for backing up to disk. If you are planning to back up to tape changer, you will have to make the tape drives and changer visible to the ZBA.
If you are running ZBA on ESX 4.x, please see this VMware Knowledgebase article.
After following instructions on the VMware KB article, you should see the tape changer and tape drive listed when you run the following command as root user on the ZBA.
# cat /proc/scsi/scsi
or
# lsscsi
Configuring Backups to Cloud
When you are configuring backups to Amazon S3 Cloud, it is important to maintain correct time on the Zmanda Backup Appliance. Backups will fail if there is a time skew. Please follow VMware Knowledgebase articleon how to keep time on VMware.
Documentation