NetBackup™ Web UI RHV Administrator's Guide
- Introducing the NetBackup web user interface
- Monitoring and notifications
- Managing RHV servers
- Configuring secure communication between the Red Hat Virtualization server and NetBackup host
- Add or browse an RHV manager
- Protecting RHV virtual machines
- Recovering RHV virtual machines
- Troubleshooting RHV VM protection and recovery
- API and command line options for RHV
- Using APIs and command line options to manage, protect, or recover RHV virtual machines
- Additional NetBackup options for RHV configuration
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
VMRedHat2are created from template
RedHat7_Templateas dependent clone and VMs
VMWin2are created from template
Windows2016_Templateas dependent clone.
While protecting these VMs, use the same backup host for all VMs based on template
Windows2016_Template. Ensure that
VMRedHat2share the same backup host. Ensure that
VMWin2share the same backup host.
VMWin2can share the same backup host, but it is optional.
The following QCOW2 image attributes are not supported:
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.