Deployment - Deploying Veeam Recovery Orchestrator

Deployment Scenarios

With its intuitive interface and comprehensive features, Veeam Recovery Orchestrator simplifies the management of disaster recovery plans and provides peace of mind for your business continuity. Installation can be performed via the setup wizard or in unattended Mode.

Though Veeam's Recovery Orchestrator can be used in various ways, it'll be essential to consider these use cases before making deployment configuration choices. This will ensure you can quickly and effectively orchestrate failovers, restores, and replication jobs. Explore the following deployment scenarios:

Orchestrating restore to Microsoft Azure from vSphere and Agent Backups

This deployment style involves setting up the Recovery Orchestrator in your environment to enable automated orchestration of restore operations to Microsoft Azure. 

It requires deploying the Recovery Orchestrator components on a dedicated VM or physical machine and configuring the necessary settings to enable communication between the Orchestrator and the Azure cloud.

Orchestrating failover based on storage replication and vSphere VMs

This deployment scenario involves setting up the Recovery Orchestrator to enable automated failover of VMs based on storage replication and vSphere VMs. 

It requires deploying the Orchestrator components on a dedicated VM or physical machine and configuring the necessary settings to enable communication between the Orchestrator and the underlying storage replication and vSphere infrastructure.

Orchestrating restore to VMware vSphere from vSphere and agent backups

This deployment style involves setting up the Recovery Orchestrator to enable automated orchestration of restore operations to VMware vSphere from vSphere and agent backups. 

It requires deploying the Orchestrator components on a dedicated VM or physical machine and configuring the necessary settings to enable communication between the Orchestrator and the vSphere infrastructure.

Orchestrating failover based on Veeam vSphere replication jobs

This deployment style involves setting up the Recovery Orchestrator to enable automated failover of VMs based on Veeam vSphere replication jobs.

It requires deploying the Orchestrator components on a dedicated VM or physical machine and configuring the necessary settings to enable communication between the Orchestrator and the Veeam replication infrastructure.

Planning for Deployment

Preparations

Successfully deploying Veeam Recovery Orchestrator starts with planning and preparation. Our first step will be ensuring we're working with supported virtualization platforms, system requirements, permissions, and network ports used for data transmission.

System Requirements: 

The machine where Orchestrator will be deployed must meet the necessary hardware and software requirements.

Operating System (64-bit Versions Only):

• Microsoft Windows Server 2025 (Veeam Backup & Replication >v12)

• Microsoft Windows Server 2022

• Microsoft Windows Server 2019

• Microsoft Windows Server 2016

• Microsoft Windows Server 2012 & 2012 R2

SQL Server:

• Microsoft SQL Server 2022

• Microsoft SQL Server 2019

• Microsoft SQL Server 2017

• Microsoft SQL Server 2016

• Microsoft SQL Server 2014

• Microsoft SQL Server 2012

Veeam Software:

• If a remote Veeam Backup & Replication server is used for backup and replication task management, it must be version 11a or later. Only connections to Veeam Backup & Replication servers deployed on Microsoft Windows Server OS are supported.

Roles & Permissions: 

Roles

There are 3 roles that you can assign to users and user groups who will work with Orchestrator. Actions a user can perform depend on the role.

• Administrator — can perform all administration actions, and can also act as a Plan Author and Plan Operator.

• Plan Author — can enable, disable, reset, create, edit and test plans.

• Plan Operator — can perform readiness checks, and can also test, schedule and run plans that are enabled.

Permissions

Considerations for access and local system administrator permissions required for the installation operation of Veeam Recovery Orchestrator include:

• Veeam Backup & Replication Servers

• Veeam Recovery Orchestrator

  • Orchestrator Service Accounts

  • Orchestrator Agent Account

  • Orchestrator User Accounts

• vCenter Server administrator permissions on the root vCenter server

• Microsoft SQL Server db_owner role required for installation and operation

Ports: 

Considerations for connection settings required for Veeam Recovery Orchestrator operation include:

• From Orchestrator Server to:

  • vCenter Server

  • Microsoft SQL Server

• From Veeam Backup & Replication Server to:

  • Orchestrator Server

  • VM Guest OS

• Workstation Web Browser to:

  • Orchestrator UI

  • Veeam ONE Reporter Web UI

• Orchestrator UI to:

  • Orchestrator Server

For a full list of default port numbers please see: VRO Ports

To verify specific and current information regarding supported virtualization platforms, system requirements, and integrations please refer to the Veeam Recovery Orchestrator Deployment guide which can be located in the Veeam Help Center.

Hardware Sizing and Scalability 

Below are guidelines that may be used to deploy the Veeam One Server on a virtual server.

The amount of required CPU and RAM resources depends on the number of systems being orchestrated in the managed infrastructure:

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.

Continue to Lesson 5: Course Completion 

Return to Course Outline