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 and a Veeam ONE server (in addition to Orchestrator functions) and, if used in this way, must have sufficient resources provided.
Important |
Consider 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:
|
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 editing, Microsoft Word component of SP2 for Microsoft Office 2010 or later is required. |
Veeam Software | If a remote Veeam Backup & Replication server is used for backup and replication task management, it must be version 11a or later. Note: Only connections to Veeam Backup & Replication servers deployed on Microsoft Windows Server OS are supported. |
[Optional] Virtualization Platform |
Notes:
|
[Optional] Storage System |
Note: Lenovo DM storage systems are also supported as they use the NetApp APIs. |
Number of Orchestrated Systems* | 0–100 | 100–1000 | 1000–5000 | 5000–10000 | >10000 |
|---|---|---|---|---|---|
CPU | 4 vCPUs (minimum) – 8 vCPUs (recommended) for the Orchestrator server 4 vCPUs (minimum) – 8 vCPUs (recommended) for all the databases | 4 vCPUs (minimum) – 8 vCPUs (recommended) for the Orchestrator server 4 vCPUs (minimum) – 8 vCPUs (recommended) for all the databases | 8 vCPUs (minimum) – 12 vCPUs (recommended) for the Orchestrator server 8 vCPUs (minimum) – 12 vCPUs (recommended) for all the databases | 12 vCPUs (minimum) – 16 vCPUs (recommended) for the Orchestrator server 12 vCPUs (minimum) – 16 vCPUs (recommended) for all the databases | >16 vCPUs for the Orchestrator server >16 vCPUs for all the databases |
Memory | 8 GB (minimum) – 10 GB (recommended) for the Orchestrator server 4 GB (minimum) – 8 GB (recommended) for all the databases | 10 GB (minimum) – 12 GB (recommended) for the Orchestrator server 4 GB (minimum) – 8 GB (recommended) for all the databases | 12 GB (minimum) – 40 GB (recommended) for the Orchestrator server 8 GB (minimum) – 40 GB (recommended) for all the databases | 30 GB (minimum) – 70 GB (recommended) for the Orchestrator server 40 GB (minimum) – 70 GB (recommended) for all the databases | >70 GB for the Orchestrator server >70 GB for all the databases |
SQL Server | N/A | 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:
Note: SSD disks are recommended to use with the Microsoft SQL Server. | ||||
