This is an archive version of the document. To get the most up-to-date information, see the current version.Architecture Overview
This section provides information on the Orchestrator architecture and its components, and describes the most common deployment scenarios. The main components in the Orchestrator infrastructure are:
- Veeam Orchestrator Server
- Veeam Backup & Replication Servers
- NetApp Storage Systems
- HPE Storage Systems
- vCenter Servers
The Orchestrator server is the configuration, administration and management core of the Orchestrator infrastructure. The Orchestrator server performs all orchestration actions. This is where orchestration plans are created, stored, tested and executed. Internally, the Orchestrator server is comprised of the following components:
- Veeam Orchestrator Server Service — is responsible for managing orchestration plans, and administering user roles and permissions.
- Veeam Orchestrator Web UI — is a web-based user interface that allows users to interact with the Veeam Orchestrator Server Service, and to perform various configuration and administration actions. In the Orchestrator UI, orchestration plans are designed, checked, tested and executed.
- Veeam Backup & Replication Server (embedded) — is included in the Orchestrator server to supply Veeam PowerShell libraries and support certain DR scenarios.
- Veeam ONE Server (embedded) — handles the ONE Business View engine to gather VM inventory. This is a custom lightweight edition of Veeam ONE that should not be used for other monitoring or reporting functions.
- SQL Server — is used to host configuration data, VM inventory and plan definitions. A Microsoft SQL Server Express instance can be installed locally with other Orchestrator components. However, for best performance and scalability, Microsoft SQL Server Enterprise edition is recommended, which may be a remote server.
All Orchestrator components can be deployed on a single Windows-based physical or virtual machine using the unified installer.
Important |
Installation of the Orchestrator server on a machine already running standalone versions of Veeam Backup & Replication and Veeam ONE is not supported. |
Veeam Backup & Replication Servers
If you already have Veeam Backup & Replication servers present in your environment, deploy an Orchestrator agent to each of these servers to orchestrate the recovery of protected VMs.
Note |
Best practice recommends that the Veeam Backup & Replication server that runs backup and replication jobs is located in the DR site. This helps you ensure that the server will not be itself lost as part of a production site outage. |
You can also use the Veeam Backup & Replication servers to create and transfer storage snapshots. For more information, see the Veeam Backup & Replication User Guide, section Snapshot Orchestration.
All NetApp storage systems must be connected to the Orchestrator server. That is, you must connect both storage virtual machines that manage volumes hosting VM disks and configuration files, and storage virtual machines that manage volumes storing replicated data.
Note |
You can connect only storage virtual machines to the Orchestrator server. Connections to NetApp clusters and nodes are not supported. |
All HPE storage systems must be connected to the Orchestrator server. That is, you must connect both storage systems that manage volumes hosting VM disks and configuration files, and storage systems that manage volumes storing replicated data.
Note |
You can connect only storage systems to the Orchestrator server. Connections to StoreServ Management Consoles are not supported. |
All vCenter Servers that manage protected VMs must be connected to the Orchestrator server.