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, VMRedHat2 are created from template RedHat7_Template as dependent clone and VMs VMWin1, VMWin2 are created from template Windows2016_Template as dependent clone.

While protecting these VMs, use the same backup host for all VMs based on template RedHat7_Template or Windows2016_Template. Ensure that VMRedHat1 and VMRedHat2 share the same backup host. Ensure that VMWin1 and VMWin2 share the same backup host.VMRedHat1, VMRedHat2, VMWin1 and VMWin2 can share the same backup host, but it is optional.

The following QCOW2 image attributes are not supported:

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.

See Error run into while backing up RHV virtual machines.

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.

For the minimum permissions required to perform VM backup and restore, see https://www.veritas.com/content/support/en_US/article.100050733