Best practices for optimal performance for your UVB and PHDVB Appliances.
To help ensure optimal performance when running Unitrends Virtual Backup in your environment, review the best practices included in this section. This article applies to all versions of PHDVB and UVB.
UVB Appliances High Availability
Since a UVB appliance must be deployed to each host, to ensure all of your VMs will be protected, the Backup appliance should remain on the host. Therefore, UVB appliances should not be configured for High Availability. If an appliance were to move off of a host due to Live Migration, the VMs on that host would no longer be protected.
When using a CIFS share as backup storage, the CIFS service account must have full permissions (read/write/delete) for the share used as the backup target. Also, antivirus software should not be configured to analyze or scan the UVB VBA CIFS storage repository.
When using an NFS share as backup storage, the UVB VBA requires direct write access to the NFS export. During backup, the UVB VBA will directly mount and copy files to the NFS share. It is important to configure the export to allow this behavior. It is strongly recommended that the backup type be Full/Incrementals and not Virtual Full to avoid NFS limitations with Hard Links and I/O performance.
Running antivirus software on a backup target can result in file locking or deletions and may cause additional issues with writing and deleting backups. UVB recommends excluding backup targets from antivirus software scans, including the network shares and directories used for backup targets.
Defragmenting virtual disks can impede the overall performance of UVB Virtual Backup, resulting in lower deduplication rates, which in turn produces larger backup files written to storage and longer backup durations. To ensure consistent backup performance, UVB recommends running disk defragmentation programs only when necessary.
Running defragmentation on any disks used as backup storage is not recommended.
Backing up the vCenter Server Virtual Machine
If your vCenter Server is running on a virtual Windows machine, to avoid interruptions and other issues, do not include the vCenter Server virtual machine within your main backup job. Instead, to back up this VM you can create a backup job with a UVB VBA that is connected directly to the host on which the vCenter Server virtual machine exists. vCenter Server VMs should be backed up only during periods of downtime when the risk of interruption is minimized.