Backup Agent Installation

Backup agents are installed on the source you want to back up or in the same network as the source you want to back up. They help interface the source data to the ZMC control plane.
The Zmanda overview covered how the backup agents integrate with the backup server and the ZMC control plane. Given we have our backup server and the ZMC control plane online, we now proceed to install the backup agents near the sources we want to back up.
The below table gives a glimpse of all the sources we support.
CentOS 8, 7 Debian 10, 9, 8 Fedora 32, 31, 30, 29, 28 Oracle Enterprise Linux 8, 7
Red Hat Enterprise Linux 8, 7 (server & desktop) Suse Linux 15.2, 12.5 Ubuntu 20.04, 18.04, 16.04
Microsoft Windows
Microsoft Windows Server 2019, 2016, 2012, 2008
Microsoft Windows 10, 8, 7
Compatible Virtualization Platforms
Hyper-V Cluster & Hyper-V Windows Server 2019, 2016, 2012
VMware vSphere 6.7, 6.5
Mac OS X
Mac OS X Server
Mac OS X 10.15, 10.14, 10.13, 10.12, 10.11, 10.10
Compatible Applications
Microsoft Exchange Server 2016, 2013
Microsoft SharePoint Server 2013
Compatible Databases
Microsoft SQL Server 2019, 2017, 2016, 2014, 2012 Oracle Server 19C, 18C, 12C on Linux Oracle Server 19C, 18C, 12C on Solaris
Oracle Server 19C, 18C, 12C on Windows PostgreSQL 12.x, 11.x, 10.x, 9.x

Methods of Installation

  1. 1.
    Agent-based: A executable service is installed directly on the source OS to backup. This installation method ensures the backup agent can actively monitor the changes done on the source system, to shorten the duration of the backup windows.
  2. 2.
    Agentless: When the source to backup doesn't contain active processing capabilities like in network-connected storage systems, or you want to back up all VMs on a hypervisor, you proceed with agentless setup. This enables the backup intelligence to be centrally located and performs backup runs from a single point of administration.