oVirt
Overview
Storware Backup & Recovery protects oVirt environments through API v4. The selected import/export mode determines how virtual machine data is backed up and restored.
Backup strategy
Data format
Incremental backup
Requirements
Disk Attachment
VM metadata in OVF format and separate disk files in RAW format
Supported through a generic incremental mechanism
A Proxy VM with the Storware Node installed in each protected cluster
Disk Image Transfer
VM metadata in OVF format and disk snapshot chains in QCOW2 format
Supported using snapshot deltas
oVirt 4.2 or later; no Proxy VM required
Changed Block Tracking (CBT)
Disk data processed using changed-block information, with zeroed sectors skipped
Supported through the dedicated CBT API
oVirt 4.4 or later, Libvirt 6+, qemu-kvm 4.2+, and VDSM 4.40+
When adding the oVirt virtualization provider, use the manager API endpoint:
https://<OVIRT_MANAGER_HOST>/ovirt-engine/apiProvide the username in user@domain format, for example admin@internal. The account must have permissions to manage snapshots, create and remove virtual machines, operate on disks, and export data.
Supported features
Supported backup strategies: Disk attachment, Image transfer, CBT (preferred)
Supported versions
4.5
4.5
4.5
The last snapshot is kept on the hypervisor for incremental backups
No
Yes
No
Access to hypervisor OS required
No
No
No
Proxy VM required
Yes
No
No
Full backup
Supported
Supported
Supported
Incremental backup
Not supported
Supported
Supported
Synthetic backups
Supported
Supported
Supported
Secondary backup destination
Supported **
Supported **
Supported
File-level restore
Supported
Supported
Supported
VM disk exclusion
Supported
Supported
Supported
Quiesced snapshots
Supported
Supported
Supported
Snapshots management
Supported
Supported
Supported
Pre/post command execution
Supported
Supported
Supported
Access to VM disk backup over iSCSI
Supported
Supported *
Supported
VM name-based policy assignment
Supported
Supported
Supported
VM tag-based policy assignment
Supported
Supported
Supported
Power-on VM after restore
Supported
Supported
Supported
* Only for RAW disk types ** Only full backup
Backup Strategies
oVirt environments can be protected in several ways.
Disk attachment with Proxy VM
In this strategy, you have a VM called “Proxy VM” that invokes commands on your hypervisor manager to snapshot and attach drives of a specific VM to itself (Proxy VM). Proxy VM is able to read the data from the attached disk snapshots and forward them to the backup provider.
This strategy allows you to exclude drives from a backup that you do not need. Remember that you need to install 1 Proxy VM per cluster so that the drives the node tries to attach are reachable.
Drawback - no incremental backup for now.

Backup Process
crash-consistent snapshot using hypervisor's API
optionally FS freeze can be executed before snapshot can be executed (FS thaw once the snapshot is completed) if enabled and guest tools installed inside
optional application consistency using pre/post snapshot command execution
metadata exported from API
snapshot disks are mounted one by one to the Proxy VM
data read directly on the Proxy VM
incremental backups are not supported
restore creates empty disks on the Proxy VM, imports merged data then recreates VM and reattaches volumes to the target VM
Disk attachment mode requires Virtio-SCSI to be enabled on the Storware Backup & Recovery Node VM (which can be enabled in VM settings -> Resource Allocation -> VirtIO-SCSI Enabled at the bottom).
During backup/restore operations, disks are transferred by attaching them to the proxy VM. This approach does not require an export storage domain to be set up.
Make sure you follow these steps: LVM setup on Storware Backup & Recovery Node for disk attachment backup mode.
Disk image transfer API
This API appeared in oVirt 4.2 and allowed the export of individual snapshots directly from the oVirt manager. So instead of having to install multiple Proxy VMs, you can have a single external Node installation, which just invokes APIs via the oVirt manager.
This strategy supports incremental backups. Assuming you have oVirt 4.2 or newer – just add your manager to Storware Backup & Recovery and the setup is done. From a network perspective, it requires two additional ports to be opened - 54322 and 54323 - and your data to be pulled from the hypervisor manager.
Unfortunately, there are a few problems with the current architecture of this solution. The biggest issue is that all traffic passes via the oVirt manager, which may impact the transfer rates that you can achieve during the backup process. To put that into perspective – in disk attachment, you can basically read data as if it is a local drive, where it could potentially be deduplicated even before it is transferred to the backup destination.

Backup Process
crash-consistent snapshot using hypervisor's API
optionally FS freeze can be executed before snapshot can be executed (FS thaw once the snapshot is completed) if enabled and guest tools installed inside
optional application consistency using pre/post snapshot command execution
metadata exported from API
data transfer initiated on the manager and actual data exported from the hypervisor using imageio API
incremental backups use the same APIs, but requests for changed blocks only
the last snapshot kept on the hypervisor for the next incremental backup (if at least one schedule assigned to the VM has the backup type set to incremental)
restore recreates VM from metadata using API and imports merged chain of data for each disk using imageio API
Disk image transfer mode exports data directly using oVirt 4.2+ API. There is no need to set up an export storage domain or setup LVM. This mode uses snapshot chains provided by oVirt.
You may need to open communication for the additional port 54323 on the oVirt manager and 54322 on the oVirt hosts - it needs to be accessible from Storware Backup & Recovery Node. Also make sure that your ovirt-imageio-proxy services are running and properly configured (you can verify it by trying to upload images with oVirt UI).
Follow the steps in this section: Full versions of libvirt/qemu packages installation.
Change Block Tracking
This is a new method which is possible thanks to changes in oVirt 4.4. It uses information about zeroed and changed blocks to reduce data size and make the process faster.

This strategy supports incremental backups.
The QCOW2 format is required for incremental backups, so disks enabled for the incremental backup will use the QCOW2 format instead of the raw format.
Also, this strategy doesn't need snapshots in the backup process. Instead, every incremental backup uses a checkpoint that is a point in time that was created after the previous backup.
Instant restore
To use an instant restore feature, backup destination from which VM will be restored, has to be of a synthetic type. The restore process creates a NFS share on the Storware Backup & Recovery node, later this share is attached to the RHV as a new storage domain. Then it creates a new virtual machine and attaches the disks from the newly created storage domain to it. To use instant restore you have to click the restore button in the instances list and choose the option instant restore.
Live migration
You can enable the live migration option during instant restore. It will automatically start the disks migration to the chosen storage after the VM is restored and powered on.
Network requirements
Disk attachment
Connection URL: https://MANAGER_HOST/ovirt-engine/api
Node
oVirt/RHV/OLVM manager
443/tcp
oVirt/RHV/OLVM API access
Disk Image Transfer
Connection URL: https://MANAGER_HOST/ovirt-engine/api
Node
oVirt/RHV/OLVM manager
443/tcp
oVirt/RHV/OLVM API access
Node
oVirt/RHV/OLVM hypervisor
54322/tcp
oVirt/RHV/OLVM ImageIO services - for data transfer (primary source)
Node
oVirt/RHV/OLVM manager
54323/tcp
oVirt/RHV/OLVM ImageIO services - for data transfer (fallback to ImageIO Proxy)
Change-Block Tracking
Connection URL: https://MANAGER_HOST/ovirt-engine/api
Node
oVirt/RHV/OLVM manager
443/tcp
oVirt/RHV/OLVM API access
Node
oVirt/RHV/OLVM hypervisor
54322/tcp
oVirt/RHV/OLVM ImageIO services - for data transfer
Node
oVirt/RHV/OLVM manager
54323/tcp
oVirt/RHV/OLVM ImageIO services - for data transfer
Last updated