The Veeam Backup for RHV architecture comprises the following set of components:
RHV manager is a Linux-based physical or virtual machine that manages RHV resources such as VMs, hosts, clusters, storage domains and networks. Veeam Backup for RHV uses the RHV manager to access RHV resources while performing backup and restore operations.
A backup server is a Windows-based physical or virtual machine on which Veeam Backup & Replication is installed. The backup server is the configuration, administration and management core of the backup infrastructure. It coordinates backup and restore operations, controls job scheduling and manages resource allocation.
A backup appliance is a Linux-based VM that resides in the RHV cluster. The backup appliance is an architecture component that sits logically between the backup server and other components of the backup infrastructure. While the backup server administers tasks, the backup appliance performs management operations, processes jobs and delivers backup traffic.
RHV Plug-in is an architecture component that enables integration between the backup server and the backup appliance. RHV Plug-in also allows the backup server to deploy and manage the backup appliance and workers.
A backup repository is a storage location where Veeam Backup for RHV stores backups of protected RHV VMs.
To communicate with backup repositories, Veeam Backup for RHV uses Veeam Data Mover — the service that is responsible for data processing and transfer. By default, Veeam Data Mover runs on the repositories themselves. If a repository cannot host Veeam Data Mover, it starts on a gateway server — a dedicated component that “bridges” the backup server and workers. For more information, see the Veeam Backup & Replication User Guide, section Gateway Server.
A worker is an auxiliary Linux-based VM that resides in the RHV cluster and processes backup workloads when transferring data to and from backup repositories.
The backup appliance comes with a preconfigured embedded worker that can be used in small virtual environments. In large environments, it is recommended to deploy dedicated workers that are distributed among the cluster hosts (nodes) and are automatically launched for the duration of a backup or restore process.