System Requirements

The machine where Orchestrator will be deployed must meet the necessary hardware and software requirements. In addition to Orchestrator functions, the Orchestrator server can function as a Veeam Backup & Replication server and a Veeam ONE server and, if used in this way, must have sufficient resources provided.

Important

Consider the following limitations:

Installation of Orchestrator on a machine already running Veeam Backup & Replication or Veeam ONE is not supported.

Installation of Orchestrator on a machine running Microsoft Windows Server Core is not supported.
Installation of Orchestrator in a PostgreSQL database is not supported.

Installation of Orchestrator server or agent on a machine with the Domain Controller role is not supported.

Specification	Requirement
Hardware	Hardware requirements depend on the size of the managed infrastructure. For more information, see Hardware Recommendations.
OS	Only 64-bit versions of the following operating systems are supported: Microsoft Windows Server 2022 Microsoft Windows Server 2019 Microsoft Windows Server 2016 Microsoft Windows Server 2012 R2 Microsoft Windows Server 2012 Orchestrator can be installed on a Windows Server OS, either domain-joined or in a workgroup.
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 Note: It is not recommended that you use the Express Edition in any production Orchestrator deployments — it should be used for product evaluation only.
Veeam Orchestrator Agent	An Orchestrator agent is required to trigger orchestration commands on remote Veeam Backup & Replication servers. The remote Veeam Backup & Replication server must meet the following requirements: The server must run Veeam Backup & Replication version 12 or later. Note that some new functionality in Orchestrator version 7.0 will not be available until the remote server is upgraded to version 12.1. The server must be deployed on a Windows Server OS. The server must run the Microsoft SQL or PostgreSQL database system. The server must belong to the same domain, to a trusted domain or to a workgroup. Note: Network address translation (NAT) between the remote Veeam Backup & Replication server and Orchestrator server is not supported.
Additional Software	All components will be installed during setup. For inline editing of report templates, Microsoft Word from Microsoft Office 2010 SP2 or later is required.
[Optional] Virtualization Platform	VMware vSphere 6.0, 6.5, 6.7, 7.0, 8.0 (up to vCenter Server 8.0 Update 2) VMware Cloud Director Notes: As direct connections to vSphere hosts are not supported, the Orchestrator server must be connected to VMware vCenter Servers. Starting from version 7.0, Orchestrator allows you to recover VMs to vCenter Servers managed by VMware Cloud Director. In this case, make sure that the Veeam Backup & Replication server that will manage the process of recovering machines to Microsoft Azure runs version 12.1 or later. Note that VMware Cloud Director cannot be used as a target recovery location.
[Optional] 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.3, 9.4, 9.5, 9.6, 9.7, 9.8, 9.9, 9.10, 9.11, 9.12, 9.13 Lenovo DM 9.3, 9.4, 9.5, 9.6, 9.7, 9.8, 9.9, 9.10, 9.11 Notes: Orchestrated failover of volumes protected by SnapMirror synchronous replication is not supported for NetApp ONTAP 9.12 or 9.13. Orchestrated failover of Consistency Groups (CG) protected by SnapMirror asynchronous replication is not supported for NetApp ONTAP 9.13. Orchestrated failover of volumes protected using SnapVault is not supported. Orchestrated failover of SVMs protected using SnapMirror is not supported.

Hardware Recommendations

Number of Protected Systems*	1–1500	1500–5000	5000–10000	10000–20000+
CPU	4 vCPUs – 8 vCPUs for the Orchestrator server 4 vCPUs – 8 vCPUs for the Microsoft SQL Server	10 vCPUs for the Orchestrator server 10 vCPUs for the Microsoft SQL Server	12 vCPUs for the Orchestrator server 12 vCPUs for the Microsoft SQL Server	>20 vCPUs for the Orchestrator server >20 vCPUs for the Microsoft SQL Server
Memory	12 GB for the Orchestrator server 8 GB for the Microsoft SQL Server	40 GB for the Orchestrator server 40 GB for the Microsoft SQL Server	70 GB for the Orchestrator server 70 GB for for the Microsoft SQL Server	>70 GB for the Orchestrator server >70 GB for the Microsoft SQL Server
SQL Server	N/A	N/A	Disk IOPS 1000 (minimum)	Disk IOPS 2000 (minimum)
Hard Disk Space	30 GB for product installation and sufficient disk space for the Veeam ONE database (if installed locally). Use the Veeam ONE Database Calculator to size application data. 20 GB for the Microsoft SQL Server. By default, the Microsoft SQL Server database grows as follows: ~1Mb per one Readiness Check Report or Plan Execution Report for a plan that includes 10 machines. ~10Mb per one Readiness Check Report or Plan Execution Report for a plan that includes 100 machines. ~100Mb per one Readiness Check Report or Plan Execution Report for a plan that includes 1000 machines. Note: SSD disks are recommended to use with the Microsoft SQL Server.

*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.