Troubleshooting of Veeam Backup for Red Hat Virtualization Deployment
- If the communication between Veeam Backup for RHV and Veeam Backup & Replication is disrupted, try the following instructions to resolve the issue: Configuring Hostname Resolution.
- If an ovirt-engine added by IP does not operate correctly, make sure an ovirt-engine and all RHEV hosts are available to the RHV backup proxy via FQDN.
- In the Red Hat Virtualization Administration Portal, You can create an incremental backup for virtual disks in the QCOW2 format. If you want to create a new virtual disk that may be included in an incremental backup, we strongly recommend to select the Enable Incremental Backup check box in the New Virtual Disk window.
If this option is unselected, the disk will be created in the RAW format. In this case, you can create a snapshot of a VM. Snapshot delta files are always created in the QCOW2 format, and the incremental backup option becomes available. Do not delete a snapshot, otherwise, the incremental backup will be disabled.
For more information, see one of the following sources:
- the article about Veeam KB
- the Incremental Backup section of the oVirt Incremental Backup Guide
- the Creating a Virtual Disk section of the oVirt Administration Guide
- During the backup of a VM all power controls are blocked. You cannot power on, power off or reboot a VM. If you change VM's power state, the backup process will fail. If this is still necessary, you can change VM's power state by one of the following methods:
- Stop a job.
- Change a power state via REST API with the FORCE option:
POST / ovirt-engine / api / vms / 123 / (shutdown / power-off / reboot)