This is an archive version of the document. To get the most up-to-date information, see the current version.

Veeam Availability Orchestrator Server

The VAO server is the configuration, administration and management core of the VAO infrastructure. The VAO server performs all orchestration actions. This is where orchestration plans are created, stored, tested and executed.

It is highly recommended that the VAO server is deployed on the DR site where VM replicas are located and where VM backups will be restored.

VAO Server Components

Internally, the VAO server is comprised of the following components:

  • VAO Server Service — is responsible for managing orchestration plans, and administering user roles and permissions.
  • VAO UI — is a web-based UI that allows users to interact with the VAO Service, and to perform various configuration and administration actions. In the VAO UI, orchestration plans are designed, checked, tested and executed.
  • Veeam Backup & Replication Server (embedded) — is included in the VAO 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 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 SQL Server Express instance can be installed locally with other VAO components. However, for best performance and scalability, SQL enterprise edition is recommended, which may be a remote server.

All VAO components can be deployed on a single Windows-based physical or virtual machine using the unified installer.

Veeam Availability Orchestrator Server Important!

Installation of the VAO server on a machine already running standalone versions of Veeam Backup & Replication and Veeam ONE is not supported.

 

Veeam Availability Orchestrator Architecture

I want to report a typo

There is a misspelling right here:

 

I want to let the Veeam Documentation Team know about that.