Agentless Installation
A backup server running in the same network as the source helps execute the backups. Helpful when the source to backup has limited processing capabilities or you seek to backup a hypervisor.
Agentless backup builds on the benefits of agent-based backup without the expense of per-server agents. Instead of installing a backup agent on each VM, the backup intelligence is centrally located and performs disk-to-disk backup from a single point of administration. This process reduces costs while simplifying administration.
For type-1 hypervisors, Zmanda licenses are based on the number of hypervisors and not on the number of VMs running on each hypervisor.

HyperV

To back up HyperV instances, you need to install the Zmanda Windows Client on the base windows OS.
Before proceeding with the installation, it's good to know that backups of HyperV VM can be done in one of two ways. Zmanda supports both of them and recommends Child VM Snapshots for production systems, given that the saved state requires downtime.
  1. 1.
    Saved state method, where snapshots of appropriate volumes are taken by putting the VM into a saved state.
  2. 2.
    Child VM Snapshot method, which backups the child VM using the VSS writers inside the Hyper-V child virtual machine.
To backup Hyper-V virtual machine, ensure Zmanda Windows Client is installed on the windows machine running your HyperV installation. Once the Zmanda Windows Client is installed, please run the below steps
  1. 1.
    Login to the ZMC server, open the Sources section, and click on “Add Source.”
Sources
2. Select Hypervisor in the side panel, and over here, we can configure our connections to the HyperV instance.
Hypervisor source
You can visit the sources page for in-depth detail for every key mapping, and to aid in quick configuration, important configurations are added below.
Host Name is the IP address or the name of the Windows Hyper-V hypervisor. Click the Discover button to discover all the virtual machines on the hypervisor.  Zmanda Windows Client must be installed on the hypervisor to discover virtual machines.  
Data Source: Users may select individual virtual machines within the Hyper-V hypervisor to backup. This will back up the virtual hard disk files (.vhd or .vhdx), snapshot files (.avhd or .avhdx), and the initial store files of the virtual machine(s) selected.
Data Deduplication, Encryption, and Compression: Select these options as desired. They are described in more detail here <add a link to sources page>.
Advanced Options: For details on the Estimate option, please refer to the backup where section, inside Backup sets. <add a link to backup set>
Once the configurations are filled in, please click on save and Zmanda will do a ping test to connect to the VM and validate the configurations. With this, you have now successfully completed mapping your HyperV install to Zmanda.

VMWare vCenter

The backup server uses vCLI and VDDK packages to interface with your vCenter instance running in the same network environment. Backup connection is established via the ESXi or vCenter credentials entered in the ZMC sources page.
Before configuring your VMWare backups on your Zmanda server, you must install vCLI and VDDK VMware packages, as Zmanda uses vCLI for interfacing with vShpere, and VDDK APIs are used for triggering backup builds. VMware would guide you through the dependencies while installing the packages, and if needed for diagnostic or manual installation, we have made a list of the dependencies below.
// for Debian systems. Use yum for rpm systems
apt install perl-Crypt-SSLeay perl-URI perl-XML-LibXML libxml2.i686 fuse fuse-libs curl openssl-devel
// for SLES 11, install the below dependencies, as openssl-devel isnt supported
zypper install perl-Crypt-SSLeay perl-URI perl-XML-LibXML libxml2.i686 fuse fuse-libs curl libopenssl-devel zlib-devel
Steps to installing vCLI and VDDK packages on the Zmanda server.
  1. 1.
    Download and extract vSphere CLI and VDDK packages from the corresponding links, vSphere CLI → https://code.vmware.com/web/tool/6.7/vsphere-cli VDDK → https://developer.vmware.com/web/sdk/7.0/vddk
  2. 2.
    Post extraction, run the install.pl files within each folder. This installs the package onto the server allowing you to connect Zmanda to the vSphere instance. If the install.py file is missing, please reach out to the VMware support team to get the needed installation script.
  3. 3.
    If you run into issues with your vCLI installation, check http_proxy and ftp_proxy environment variables to check if they are empty if Zmanda Server has a direct connection to the internet, or if the proxy IP address is entered correctly for proxy configurations.
Now that we have the dependencies taken care of, there are two things to note before we begin installations.
  1. 1.
    If the VMware commands (vmware-cmd, vmkfs, vmware-diskmanager, snapshotmanager.pl) are not installed in default locations (/usr/lib/vmware-vcli for VCLI and /usr/bin for vmware-diskmanager), you will have to modify /etc/zmanda/aee4/zmc_user_dumptypes to fix the application properties (VCLI-PATH, VCLI-BIN-PATH and VDDK-BIN_PATH).
  2. 2.
    If you have multiple VMs in your ESXi installation, we recommend creating an individual source for every VM in your ESXi instance for better long-term management.
Please run the steps below to begin linking Zmanda to ESXi/vCenter server.
  1. 1.
    Login to the ZMC server, open the Sources section, and click on “Add Source”.
Add source
2. Select Hypervisor in the side panel, and then select VMware in the first dropdown. The figure below diagram shows all the possible configurations for VMWare.
Configuration page for VMWare connection
You can visit the sources page for in-depth detail for every key mapping, and to aid in quick configuration, important configurations are added below.
ESX/vCenter Hostname is the name of the ESX server whose guest VMs are being backed up or the VMware vCenter that manages the ESX server.  It can be the IP address or the IP name.
The hostName is the name of the guest VM that should be backed up. You should not use the IP address of the guest VM.  This is the VM Display name (not the name of the data storage folder on the ESX server) as shown in the left panel in the Vsphere Client. This value is case-sensitive. If ESX Host Name is VMware vCenter, the VM can reside on any ESX server managed by the vCenter.
VCenter/ESX Username and VCenter/ESX Password is the authentication information for the ESX server or VMware vCenter Server. The user account must be local to the ESX server (login to the ESX server and create the VMware user) not a vCenter-wide/domain account used on the ESX server.
Once the configurations are filled in, please click on save, and Zmanda will do a ping test to connect to the VM and validate the configurations. With this, you have now successfully completed mapping your VMWare install to Zmanda.

NFS/iSCSI/Lustre File System

Once the storage is mounted on the server, you add the path of the mounted directory in the sources tab. It's the most versatile form of file-level backup.
This is the easiest form of backup, as the files or folders to be backed-up are attached to the Zmanda server itself. Thus, if you have any licensed version of Zmanda, you can configure NFS Backups by running through the below steps
  1. 1.
    Visit the sources page on ZMC, and click on add sources. In the pop-out, please select Filesystem and then select NFS/iSCSI/Lustre from the type dropdown.
  2. 2.
    Once you fill in the details on the screen, click on save, with that, your NFS/ iSCSI/ Lustre file systems are ready to be backed up.
NFS/iSCSI/Lustre systems source creation

CIFS Share

You can mount the share to a Zmanda Backup Server, to take backups via NFS, or install Samba packages on the backup server to interface with Samba server and Samba shares.
CIFS Shares can be mounted onto the Zmanda server for direct backups or done via the network using the Samba protocol.
  1. 1.
    Once the CIFS share is mounted to the Zmanda server, you can backup your CIFS Share as a regular Network Attached File Storage system, and more details on how to configure NFS are added in the NFS section of this page. This process, however cannot be used for performing incremental backups, as amgtar backup of CIFS shares does not retain inode numbers across mounts.
  2. 2.
    To backup via the network, Samba protocol is used where Samba, Samba common, and Samba Client packages are installed on the backup server. Incremental backups are supported in this process, as archive bits are used to identify changes.
The steps to back up your CIFS share via the Samba protocol.
  1. 1.
    Install samba and samba-client on the system running ZMC and make sure smb service is active. Zmanda assumes that the smbclient executable binary file is located in /usr/bin on the Zmanda server. If smbclient is not in /usr/bin, create a symbolic link to the file in that directory.
  2. 2.
    Given the dependences are taken care of, you can open the Sources tab in ZMC and click on “Add Source”. In the popout window, select File systems, and then select Network/CIFS share, and you should see a screen like the below.
Network/CIFS Share source creation
3. For quick configuration, we have listed the most important values below. For a complete guide, please visit the sources page.
  1. 1.
    Host Name
    Specifies the host name of Zmanda Server. For better backup performance, Zmanda recommends using the Zmanda server itself as  localhost. If you want to do the backup from the remote client attached to the CIFS Share, then you need to create a file at /etc/amanda/backup_set_name/cifs_network_shares  on the remote client, which can be an identical clone of this file on the Zmanda server /etc/amanda/backup_set_name/cifs_network_shares.client_name.
  2. 2.
    Share Name The CIFS share is represented in Universal Naming Convention format with the format being \\CIFSserver\share\sub-directory . The CIFSserver can be specified as an host name or IP address. This is the share backed that will be backed up by Zmanda.
4. Once the configurations are filled in, please click on save and Zmanda will do a test to connect to the CIFS Share and validate the configurations. With this, you have now successfully completed mapping your CIFS Share to Zmanda.

NDMP

Zmanda acts as a backup controller, allowing data to flow directly to the storage destination. It allows for reduced network congestion in large-scale backup implementations.
Zmanda supports remote, direct, and 3-way NDMP configurations running on the NDMPv4 protocol.
In Remote NDMP configurations, NDMP appliances such as Netapp Filers, Sun Unified Storage, EMC Celera, and BlueArc storage are backed up. Backup data in remote NDMP configuration runs through Zmanda servers, as a temp storage space is needed before data is loaded to tape changers or disks attached to the Amanda server. In Direct or 3-way NDMP configurations, Zmanda acts as a backup control program, and thus data directly moves from the source to the destination, reducing LAN congestion and optimizing the resources on the Zmanda server.
Performing backup runs on your NDMP devices
  1. 1.
    Open the Sources tab in ZMC and click on “Add Source.” In the popout window, select File systems, and then select NDMP in the type.
Add Source
2. The following figure shows an example backup configuration of /vol/zmanda_fs1 from Netapp Filer with IP address 192.168.29.151.
NDMP source creation
3. Once the configurations are done, please click on save. The NDMP device will be validated in the background, and with this, you have officially connected your NDMP appliance to Zmanda.
If your NDMP device is not being discovered, then below are the most common issues we have noticed.
  • If there is a firewall on the Zmanda server, a firewall rule should be added to trust each NDMP device being backed up.
  • NDMP services must be enabled on the appliance. For example, the following figure shows how to check if NDMP services are enabled on BlueArc Storage.
Check if NDMP services are enabled on BlueArc Storage
Export as PDF
Copy link
On this page
HyperV
VMWare vCenter
NFS/iSCSI/Lustre File System
CIFS Share
NDMP