This is an archive version of the document. To get the most up-to-date information, see the current version.System Requirements
The machine where Orchestrator will be deployed must meet the necessary hardware and software requirements. Note that the Orchestrator server can function as a Veeam Backup & Replication server (in addition to Orchestrator functions) and must have sufficient resources provided.
Important |
Mind the following limitations:
|
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:
Note: It is not recommended to install Orchestrator on a machine running Microsoft Windows Server Core. |
User Management | Windows domain-joined machine |
SQL Server | Local or remote installations of the following versions of Microsoft SQL Server are supported:
Note: It is not recommended to use the Express Edition in any production Orchestrator deployments — it should be used for product evaluation only. |
Additional Software | All components will be installed during setup. For inline Report Template editing, Microsoft Word component of SP2 for Microsoft Office 2010 or later is required. |
Veeam Software | If a standalone Veeam Backup & Replication server is used for backup and replication task management, it must be version 11 or later. Version 11a is fully supported. Note: If you connect a standalone Veeam Backup & Replication server to the Orchestrator server, it must be joined to either the same domain, a trusted domain or a workgroup. Only connections to Veeam Backup & Replication servers deployed on Microsoft Windows Server OS are supported. |
Virtualization Platform |
Note: The Orchestrator server must be connected to VMware vCenter Servers. Direct connections to vSphere hosts are not supported. |
Storage System |
Note: Lenovo DM storage systems are also supported. |
Number of Virtualization Hosts* | 100 | 100–500 | 500–1000 | >1000 |
|---|---|---|---|---|
CPU | 6 vCPUs (minimum) – 8 vCPUs (recommended) for the Orchestrator server 4 vCPUs (minimum) – 8 vCPUs (recommended) for the Microsoft SQL Server and Veeam ONE database | 8 vCPUs (minimum) – 12 vCPUs (recommended) for the Orchestrator server 8 vCPUs (minimum) – 12 vCPUs (recommended) for the Microsoft SQL Server and Veeam ONE database | 12 vCPUs (minimum) – 16 vCPUs (recommended) for the Orchestrator server 12 vCPUs (minimum) – 16 vCPUs (recommended) for the Microsoft SQL Server and Veeam ONE database | >16 vCPUs for the Orchestrator server >16 vCPUs for the Microsoft SQL Server and Veeam ONE database |
Memory | 6 GB (minimum) – 8 GB (recommended) for the Orchestrator server 4 GB (minimum) – 8 GB (recommended) for the Microsoft SQL Server and Veeam ONE database | 8 GB (minimum) – 40 GB (recommended) for the Orchestrator server 8 GB (minimum) – 40 GB (recommended) for the Microsoft SQL Server and Veeam ONE database | 40 GB (minimum) – 70 GB (recommended) for the Orchestrator server 40 GB (minimum) – 70 GB (recommended) for the Microsoft SQL Server and Veeam ONE database | >70 GB for the Orchestrator server >70 GB for the Microsoft SQL Server and Veeam ONE database |
Hard Disk Space | 50 GB for product installation and sufficient disk space for the Microsoft SQL Server and Veeam ONE database (if installed locally). Use the Veeam ONE Database Calculator to size application data. | |||
* Under the condition that one host has 20 VMs deployed.