Things to know before you protect RHV virtual machines
You cannot backup the same RHV VM concurrently.
The VMs without virtual disks cannot be protected.
Ensure to use the same backup host to backup all template-based VMs (dependent clone).
For example, VMs
VMRedHat1,VMRedHat2are created from templateRedHat7_Templateas dependent clone and VMsVMWin1,VMWin2are created from templateWindows2016_Templateas dependent clone.While protecting these VMs, use the same backup host for all VMs based on template
RedHat7_TemplateorWindows2016_Template. Ensure thatVMRedHat1andVMRedHat2share the same backup host. Ensure thatVMWin1andVMWin2share the same backup host.VMRedHat1,VMRedHat2,VMWin1andVMWin2can share the same backup host, but it is optional.The following QCOW2 image attributes are not supported:
Compressed cluster
Encrypted disks
Virtual disks with internal snapshots
If the VM virtual disks are locked when the NetBackup services shutdown or crash during a backup, use RHV's unlock_entity command to unlock the disks. If the disks are not unlocked, the subsequent backups might fail.
On a file storage (NFS), a QCOW2 disk gets restored as raw disk (thin provision) because of an RHV limitation.
A thin dependent cloned VM is restored as an independent cloned VM.
If you want to use a storage that is not available through the NetBackup Web UI like a tape or basic disk based storage unit, you can use APIs or command line options to protect the VMs.