Veeam Recovery Orchestrator 7.2 Release Notes

This document provides last-minute information about Veeam Recovery Orchestrator (Orchestrator), including system requirements and relevant information on technical support, documentation, online resources and so on.

The current version of Veeam Recovery Orchestrator is available for download at https://www.veeam.com/downloads.html from July 17th, 2025.

System Requirements

Unless otherwise stated, all 3rd party software must be at the latest update or patch level.

Hardware

Hardware requirements depend on the size of the managed infrastructure.

*The total number of systems protected by replicas and backups (including Veeam agent and VMware vSphere VM backups). Assumes one restore point per system per day.

OS

Only 64-bit versions of the following server operating systems are supported:

• Microsoft Windows Server 2025
• Microsoft Windows Server 2022
• Microsoft Windows Server 2019
• Microsoft Windows Server 2016
• Microsoft Windows Server 2012 R2
• Microsoft Windows Server 2012

Installation on a machine running Microsoft Windows Server Core or on a Domain Controller is not supported.

Microsoft SQL Server

Local and remote installations of the following versions of Microsoft SQL Server are supported:

• Microsoft SQL Server 2022
• Microsoft SQL Server 2019
• Microsoft SQL Server 2017 (2017 SP2 Express Edition is included in the setup)
• Microsoft SQL Server 2016
• Microsoft SQL Server 2014
• Microsoft SQL Server 2012

It is not recommended to use the Express Edition in a production Orchestrator deployment — it should only be used for product evaluation and testing.

Veeam Orchestrator agent

The Veeam Orchestrator Agent is required to trigger orchestration actions on remote Veeam Backup & Replication servers. The remote Veeam Backup & Replication server must be:

• Running on a Windows Server OS
• Running version 12.x

Some new functionality in Orchestrator version 7.2 will not be available until connected Veeam Backup servers are upgraded to 12.3.

Additional software

For inline editing of report templates, Microsoft Word from Microsoft Office 2010 SP2 or later is required.

VMware

• VMware vSphere 6.0, 6.5, 6.7, 7.0, 8.0, 9.0

  The Orchestrator server must be connected to VMware vCenter Servers only. Direct connections to vSphere hosts are not supported.

• VMware Cloud Director

  Previous versions of Orchestrator did not support orchestration of vCenter Servers that were managed by VMware vCloud Director. In version 7.0, this has been addressed. Although vCloud Director itself cannot be used as a target recovery location, Orchestrator will fully support recovery to the connected vCenter Servers. The version of Veeam Backup & Replication must be 12.1 or later.

Hyper-V

• System Center Virtual Machine Manager (SCVMM) 2022 and 2025
• Hyper-V Windows Server 2022 and 2025
• Azure Local (formerly Azure Stack HCI) 23H2 or later

  The Orchestrator server can connect to Hyper-V and Azure Local clusters either directly, or via SCVMM

Microsoft Azure connected through Veeam Backup & Replication

To orchestrate recovery of Veeam agent or vSphere VM backups to Microsoft Azure, the connected Veeam Backup & Replication servers must have cloud credentials added for a Microsoft Azure compute account.

Storage system

• HPE 3PAR 3.3.1, 3.3.2 MU1
• HPE Primera 4.2, 4.3, 4.4, 4.5
• HPE Alletra 9000
• NetApp ONTAP 9.7, 9.8, 9.9, 9.10, 9.11, 9.12, 9.13, 9.14, 9.15, 9.16
• Lenovo DM/DG Series 9.7, 9.8, 9.9, 9.10, 9.11, 9.13, 9.14, 9.15, 9.16

Required Permissions

The accounts used for installing and using Veeam Recovery Orchestrator must have the following permissions.

What’s New in Veeam Recovery Orchestrator 7.2.1

Support for Microsoft Azure Local (formerly Azure Stack HCI) as a restore target

VRO 7.2.1 extends support for Microsoft platforms by allowing Azure Local clusters in recovery locations. Clusters can be connected directly to VRO with or without SCVMM.

This capability extends to Hyper-V clusters too, which can now be connected directly to VRO without any SCVMM requirement. Note that a cluster must be connected to VRO via only one methdod - directly, or via SCVMM connection.

VRO restore plans can now be created for Hyper-V or Azure Local VMs, which can be recovered to their original location or to a new Hyper-V /Azure Local cluster location. Existing VRO restore plans for VMware vSphere VM backups can also use the new Hyper-V and Azure Local recovery locations, allowing cross-platform recovery and migration.

VRO restore plans for Hyper-V include the following features:

• Plan creation using groups based on SCVMM Tags & Hyper-V backup jobs, or vCenter Tags & vSphere VM backup jobs
• Daily readiness checks to confirm RPO & infrastructure availability
• Daily Plan Definition reports including detailed change log and plan configuration
• Plan Execution with RTO + RPO measurement, malware flag check, post-recovery confirmation (heartbeat checking), and detailed reporting.

The following features are not yet implemented for Azure Local / Hyper-V in Orchestrator and will be added in a future update:

• Replica failover plans
• Active malware/virus/YARA scan during restore
• Virtual lab testing
• In-guest script execution during recovery (this limits the execution of certain built-in recovery steps, and custom script steps)

For SCVMM environments, the SCVMM console must be installed on the Orchestrator server to facilitate the integration.

Multi-factor authentication (MFA)

MFA can be enabled and disabled globally in the Scope Users page in the administration section. It will be enforced for login to the VRO web UI (it is not currently enforced for plan executions, which will still prompt for password) Microsoft and Google authentication apps are supported.

Known Issues

MFA

Enabling MFA after upgrading to version 7.2.1.286 results in a login error preventing user access. This issue has been resolved in build 7.2.1.290 that is available for download. If you have already upgraded to 7.2.1.286, please contact technical support for assistance — reinstallation is not required.

Hyper-V recovery

Considerations when connecting Orchestrator to SCVMM

When a connection is created to SCVMM in the Orchestrator UI, this connection is automatically pushed to the embedded Veeam ONE server and the emdedded Veeam Backup server. The Veeam Backup server will deploy connectivity components to the Hyper-V hosts as part of the usual process of registering this connection. If there is already a Veeam Backup server of an older version which has a connection to this SCVMM and these hosts, it will lose connection and backups and restores will fail, due to the mismatch of installed component versions.

It is essential to upgrade any existing Veeam Backup servers to the same version as the embedded Veeam Backup server on Orchestrator before creating the SCVMM connection in Orchestrator. In this way on-host components will already be the correct version.

Cluster networks

If a specific host or hosts are not responding when the cluster is added to VRO infrastructure; or if a host is excluded from monitoring in the Veeam ONE console, then VRO may fail to collect all the cluster networks for use in mapping rules.

CSV storage

Orchestrator cannot retrieve the online/offline status of CSV disks in Hyper-V recovery locations. Disks chosen in the location configuration will be assumed online and used for restore. An active check of CSV status will be introduced in a future update.

Plan Steps compatibility

As in-guest scripting is not yet supported when recovering Hyper-V VMs, some plan steps that can be used when restoring vSphere backups will not be compatible when restoring Hyper-V backups. The full list impacted steps can be found in the [User Guide][link] In-guest scripting will be added in a future update.

Heartbeat check post-restore

Heartbeat check of a restored VM is included for Hyper-V, however if the cluster resource optimization is set very aggressively the restored VM maybe migrated from the host it was restored to before Orchestrator can complete the heartbeat check. Additionally, heartbeat check may be unreliable when there are a laerge number of host servers in the cluster. For this reason, the Check Heartbeat step is not automatically added when creating a Hyper-V restore plan; however the step can be added afterwards, and tuned according to the environment.

Scalability

It is not recommended to exceed the default setting of 10 VMs processed in parallel when the recovery location is a Hyper-V cluster. This is due to queuing and contention in the Veeam PowerShell cmdlets which can cause commands to eventually time out. Optimization is in progress for a future update.

Setup

If a new license is supplied during VRO upgrade, it will not be applied to the embedded Veeam ONE server. The workaround is to open the Veeam ONE console after upgrade and apply the correct license manually.

If installing on Windows Server 2025, and choosing the option to install a new instance of SQL Express, a command prompt window will appear during the first step of the installation. To ensure a successful installation, minimize/ignore this window. This is caused by the SQL Express installer ignoring ‘-silent’ switches during installation on Server 2025. The issue has been raised with Microsoft.

Upgrade

• Customers who have applied a private fix or patch to the embedded Veeam Backup server installed on the Orchestrator server will find that upgrade using the setup wizard will fail. Perform upgrade by launching the VRO .msi installer directly. For assistance contact Veeam Support.
• The following configuration checks have been added to the upgrade wizard:
  • Each VRO plan should require only a single Veeam Backup server to execute. Although Orchestrator does (and will continue to) support orchestration of multiple Veeam Backup servers, historically it was possible to create plans where more than one Veeam Backup server was needed for recovery of a single plan (for example one group of VMs in the plan is protected by server A, another group is protected by server B).

    This configuration is not recommended, as such plans would be impossible to test - as testing requires a Virtual Lab, which can only be managed by a single Veeam Backup server. Due to this and other similar configuration and execution issues, all plans should require a single backup server.

  • Each VRO Restore plan should restore only a single type of backup, where type is vSphere VM backup or Veeam Agent backup. This will also be enforced for new Hyper-V restore plans going forward. This is required to support additional cross-platform functionality and ensure stable plan performance. If existing plans contain VM Groups based on different backup types, the plan can be cloned and then both copies edited to support the new configuration.

    Note that the resultant two plans can then be run simultaneously; there is no restriction on restoring different types of backup at the same time. The restriction is only that they should not be in the same plan.

• If you try to upgrade Orchestrator to version 7.2 while the existing Orchestrator 7.1 databases are protected with SQL replication, the upgrade process will fail with an error. This is a known issue related to specific aspects of SQL replication.
• During the upgrade, some warning dialogs with text including “Improved background retention” and “Active CDP Policy” may be displayed. These are warnings related to the embedded Veeam Backup & Replication server and may appear if that server has been used for general backup and replication tasks. For full details of the actions to take upon any warning messages, see the Veeam Backup & Replication User Guide, section Upgrading to Veeam Backup & Replication 12.

Infrastructure

• SQL authentication credentials provided during Orchestrator server installation cannot be changed. If the password for the SQL account is changed, Orchestrator will be unable to connect to the database. To work around the issue, it is recommended to use Windows Authentication to connect to the Microsoft SQL Server. Alternatively, Veeam Customer Support can help you resolve the issue.

Recovery plans

• The maximum value for parallel processing of VM recoveries in a recovery plan is capped at 50 (previously 99). This is due to limitations in asynchronous processing in the PowerShell engine for Hyper-V specifically; however the limit is imposed on all plan types. It is planned to remove this limit in the next major version update. If you require a higher limit please contact Veeam Customer Support.
• Existing failover plans may require modification to meet new configuration rules. Each single plan should require only one Veeam Backup server to execute; and any Restore plan should recover only one type of backup. More details are in the upgrade section above.
• If a plan includes in-guest scripts and the source machine is still online, you may see the following error when executing the script step: “RPC error: There are no more endpoints available from the endpoint mapper”. This is caused by the Veeam Backup & Replication server attempting to deliver the script to the source machine. The expectation during a recovery plan execution is that the source machine is not available. Note if this error occurs during plan testing, it is a sign that the DataLab configuration is not correct.

Storage failover

• Under certain circumstances, a plan may be halted after one or more Register VM steps have started but not completed, causing orphaned VMs to be created in the recovery location. These VMs should be removed manually. The issue will be addressed in a future update.

Technical Documentation References

If you have any questions about Veeam Recovery Orchestrator, you may use the following resources:

• Product web page
• Veeam Data Platform web page

Technical Support

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

• Version information for the product and its components
• Error message and/or accurate description of the problem you are having
• Log files

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.