Veeam Backup for Oracle Linux Virtualization Manager and Red Hat Virtualization 4.1
Release Notes
User Guide

Veeam Backup for Oracle Linux Virtualization Manager and Red Hat Virtualization 4.1 Release Notes

This document provides last-minute information about Veeam Backup for Oracle Linux Virtualization Manager and Red Hat Virtualization (Veeam Backup for OLVM and RHV) 4.1, including system requirements and installation, as well as relevant information on technical support, documentation, online resources and so on.

For existing deployments, Veeam Backup for Red Hat Virtualization version 2, 2a, 3, 3a and 3b is automatically upgraded to version 4.0 together with the upgrade of Veeam Backup & Replication to version 12.1. Then, oVirt KVM Plug-in for Veeam Backup & Replication must be installed to upgrade Veeam Backup for Red Hat Virtualization to Veeam Backup for OLVM and RHV 4.1.

For new deployments, the release version of Veeam Backup for OLVM and RHV 4.1 is available for download from the Veeam downloads page starting from April 2nd, 2024.

See next:

System Requirements

Platform

Red Hat Virtualization

  • Red Hat Virtualization version 4.4 SP1 (Red Hat Virtualization Manager 4.5.0 and later)
  • Red Hat Virtualization node operating version 4.5
  • Red Hat Virtualization cluster compatibility version 4.7

To learn how to configure the cluster compatibility version, see Red Hat Virtualization documentation.

Oracle Linux KVM

  • Oracle Linux Virtualization Manager version 4.5.4 and later
  • Oracle Linux Virtualization node operating version 4.5
  • Oracle Linux Virtualization cluster compatibility version 4.7

To learn how to configure the cluster compatibility version, see Oracle Linux Virtualization Manager documentation.

Virtual Hardware for VMs

During the deployment process, the Veeam Backup for OLVM and RHV Backup Appliance (backup appliance) is deployed on a KVM host as a dedicated Linux-based VM. The backup appliance configuration determines the maximum number of tasks (backup or restore sessions) that the backup appliance can handle in parallel. If this number is exceeded, the backup appliance will not start a new task until one of the current tasks finishes. By default, the backup appliance supports 4 concurrent tasks and runs on a VM with the following configuration:

  • CPU: 4 vCPU
  • Memory: 4 GB RAM
  • Disk Space: 100 GB for product installation, internal database files, logs, and other data

The maximum number of concurrent tasks can be increased; however, additional resources must be allocated: 1 vCPU and 1 GB RAM for each additional task. When configuring the maximum number of concurrent tasks, consider the network traffic throughput in your virtual infrastructure.

For large deployments, it is recommended to configure dedicated workers that perform data processing tasks. Workers are Linux-based VMs that are distributed among the cluster hosts (nodes) and are automatically launched for the duration of a backup or restore process. VMs running as dedicated workers must be allocated the following compute resources for each concurrent task:

  • CPU: 1 vCPU
  • Memory: 1 GB RAM

oVirt KVM Plug-in for Veeam Backup & Replication

Veeam Backup for OLVM and RHV 4.1 includes oVirt KVM Plug-in 12.4.1.45 and backup appliance 4.0.1.108.

The oVirt KVM backup appliance requires integration with oVirt KVM Plug-in installed on the Veeam Backup & Replication 12.1 server.

Known Issues and Limitations

Oracle Linux KVM

Red Hat Virtualization 4.4 SP1 Known Issues

Data Protection

  • Veeam Backup for OLVM and RHV does not create application-consistent backups. You can use Veeam Agent for Linux or Veeam Agent for Windows to create application-consistent backups.
  • Veeam Backup for OLVM and RHV supports VM backups with mixed virtual disks: RAW and QCOW2.
  • By default, Veeam Backup for OLVM and RHV applies the following deduplication and compression settings to backed-up data:

    • Deduplication: Enabled
    • Data compression level: Optimal
    • Storage optimization: 1MB

    Due to technical limitations, you cannot change these settings while configuring backup jobs.

  • By default, backup encryption is disabled for backed-up data. However, you can enable encryption at the repository level. For more information, see the Access Permissions section of the Veeam Backup & Replication User Guide.
  • A repeated Health Check of the corrupted data returns a green session (disk is skipped from processing).
  • Backup Copy exclusions does not accept oVirt KVM jobs and objects. 
  • VeeamZIP retention is not supported. 
  • You cannot back up a VM while previewing its snapshot.
  • You can back up each VM with one backup job at a time. If a VM is already being processed by a backup job, another backup job will not start processing this VM unless the currently running backup operation completes.
  • You cannot include into a backup job a VM being backed up by 3rd party software or a backup appliance connected to another backup server. Wait for the backup process to complete or stop the job manually, and then add the VM to a backup job.
  • Since Veeam Backup & Replication does not allow you to assign information about locations to Virtualization Managers and backup proxies, job statistics do not include information on the oVirt VM data migration between different geographic regions.
  • Manual Move backup functionality is not supported for oVirt KVM backups.
  • If you want to back up a VM that has been configured with a oVirt KVM Cloud-Init custom script, first remove the script from the VM since it may contain secure data (such as credentials and authorized keys) that will appear in Veeam Backup for OLVM and RHV backup logs.
  • To send email notifications on backup job results, Veeam Backup for OLVM and RHV uses account settings configured in the Veeam Backup & Replication console. However, mail servers with SMTP basic authentication are only supported.
  • Starting from version 4.1, Veeam Backup for OLVM and RHV uses disk alias for configuring disk exclusions in backup jobs.
  • Veeam Cloud Connect repositories are not supported as backup repositories for Veeam Backup for OLVM and RHV.

Data Recovery

  • You can perform Instant Recovery to VMware, Hyper-V, Nutanix AHV hosts from backups created by Veeam Backup for OLVM and RHV. VMware vSphere, Hyper-V or Nutanix AHV hosts must be added to the Veeam Backup & Replication backup infrastructure.
  • Veeam Backup for OLVM and RHV supports restore from another oVirt instance for the imported backups.
  • While restoring an oVirt VM with the QXL GPU device to the Oracle Linux KVM environment, Veeam Backup for OLVM and RHV changes the GPU device to VGA.
  • While restoring an oVirt VM with the CIRRUS VGA GPU device to the Red Hat Virtualization environment, Veeam Backup for OLVM and RHV changes the GPU device to VGA.
  • If you perform the revert to a snapshot operation, during the next session, Veeam Backup for OLVM and RHV runs a full scan of the VM disks and creates an incremental backup.
  • If a VM added to the restore session contains multiple disks, Veeam Backup for OLVM and RHV restores one disk per job at a time.

Recovery Verification

SureBackup for backups created by Veeam Backup for OLVM and RHV is supported in the Backup verification and content scan only verification mode.

Veeam Backup Enterprise Manager

You can use Veeam Backup Enterprise Manager to file-level restore guest OS files of oVirt VMs and manage oVirt VM backup copy jobs. All other operations are not supported.

Deploying Veeam Backup for OLVM and RHV

To deploy Veeam Backup for OLVM and RHV 4.1, do the following:

  1. Install Veeam Backup & Replication 12.1 and configure a backup repository that will be used as a target for VM backups.
  2. Download oVirt KVM Plug-in for Veeam Backup & Replication from the Veeam downloads page.
  3. Install oVirt KVM Plug-in for Veeam Backup & Replication.
  4. In the Veeam Backup & Replication console, add the Virtualization Manager to the backup infrastructure.
  5. In the Veeam Backup & Replication console, complete a wizard to deploy a new oVirt KVM backup appliance or connect an existing one.
  6. Deploy dedicated workers.

For detailed instructions, see the Deployment section of the Veeam Backup for OLVM and RHV User Guide.

Upgrading Veeam Backup for Red Hat Virtualization

Veeam Backup for Red Hat Virtualization version 2, 2a, 3, 3a, 3b and 4.0 can be upgraded to Veeam Backup for OLVM and RHV version 4.1.

If you use Veeam Backup & Replication 11 and you want to upgrade Veeam Backup for Red Hat Virtualization version 2.0 or 2a to version 4.0, upgrade Veeam Backup & Replication to version 12.1:

  1. Check the prerequisites and upgrade Veeam Backup & Replication to version 12.1. For instructions on how to do it, see Upgrading to Veeam Backup & Replication 12 section of the Veeam Backup & Replication User Guide.
  2. During the process of upgrading to Veeam Backup & Replication 12.1, the wizard will automatically upgrade Red Hat Virtualization Plug-in to version 4.0.
  3. Download oVirt KVM Plug-in for Veeam Backup & Replication from the Veeam downloads page.
  4. Install oVirt KVM Plug-in for Veeam Backup & Replication.
  5. Open the Veeam Backup & Replication console. The upgrade wizard will appear and prompt you to upgrade the product components. Follow the wizard to complete the upgrade process for oVirt KVM backup infrastructure components.

Note that Veeam Backup for Red Hat Virtualization 1.0 cannot be upgraded to Veeam Backup for OLVM and RHV version 4.1. First, you must upgrade it to version 2a as described in the Veeam Backup for Veeam Backup for Red Hat Virtualization 2.0 User Guide, section Upgrading to Veeam Backup for RHV 2a.

Licensing

Veeam Backup for OLVM and RHV is licensed by the number of protected oVirt VMs. Each protected oVirt VM consumes one Veeam Universal License instance from the license scope. An oVirt VM is considered protected if it has a restore point created during the past 31 days. For more information, the Licensing section of the Veeam Backup for OLVM and RHV User Guide.

To renew your maintenance plan, please contact Veeam Renewals.

Technical Documentation References

If you have any questions about Veeam Backup for OLVM and RHV, you may use the following resources:

Technical Support

We offer email and phone technical support for customers on maintenance and during the official evaluation period. For better experience, please provide the following information when contacting Veeam Customer Support:

  • Version information for the product and all infrastructure components
  • The error message and an accurate description of the problem you are having
  • Log files

TIP

To export the log files, from the main menu of the Veeam Backup & Replication console, select Help > Support Information. At the Scope step of the Export Logs wizard, select the Export all logs for selected components option. Then, in the Managed servers list, select the backup server and the VM running as the oVirt KVM backup appliance, and complete the wizard.

To submit your support ticket or obtain additional information, please visit the Veeam Customer Support Portal. Before contacting Veeam Customer Support, consider searching for a resolution on Veeam R&D Forums.

Contacting Veeam Software

At Veeam Software, we pay close attention to comments from our customers — we make it our mission to listen to your input, and to build our products with your suggestions in mind. We encourage all customers to join Veeam R&D Forums and share their feedback directly with the R&D team.

Should you have a technical or licensing issue or question, please feel free to contact our Customer Support organization directly. We have qualified technical and customer support staff available 24/7 who will help you with any inquiry that you may have.

Customer Support

For the most up to date information about our support practices, business hours and contact details, please visit the Veeam Customer Support Portal.

Company Contacts

For the most up to date information about company contacts and office locations, please visit the Veeam Contacts Webpage.

Document updated: 4/18/2024

View all results across Veeam
Back to document search