Migrating VAO 1.0 Deployment to Version 2.0

Challenge

Upgrade of Veeam Availability Orchestrator to version 2.0 is not supported. However, you have an option to migrate your VAO 1.0 configuration to version 2.0 with minimal downtime. 

This KB article briefly describes architectural changes introduced in 2.0 version and provides step-by-step instructions on how to perform VAO migration.
 

Cause

The concept of VAO sites is no longer supported in version 2.0. To provide administrative role-based delegation, VAO now uses scopes. A scope is a logical unit introduced to determine operations that can be performed by VAO users and to define the items available to these users.

If you have a multi-server VAO 1.0 deployment and want to migrate to version 2.0, your main concern now is to configure a list of scopes that will match the preceding Production site configuration.  

To learn more about VAO scopes, see the Veeam Availability Orchestrator 2.0 User Guide, section Managing Permissions.
 

Solution

Planning and Preparation

1. Make sure the machine on which VAO will be deployed has no other Veeam components installed, and meets the hardware and software requirements listed in the Veeam Availability Orchestrator 2.0 Deployment Guide, section System Requirements.
2. Make sure the accounts used to install and use the VAO solution have the permissions described in the Veeam Availability Orchestrator 2.0 Deployment Guide, section Required Permissions.
3. Make sure the ports used to ensure proper communication of VAO components are opened as described in the Veeam Availability Orchestrator 2.0 Deployment Guide, section Ports.
4. Make sure you have a valid license for VAO 2.0 that covers the required number of licensed VMs. Otherwise, you can obtain the latest license key either by logging in to the Veeam website using your credentials or by contacting our Licensing Department. To contact the Licensing Department, open the Veeam Support Resources webpage, click Submit a ticket, and select Licensing to receive assistance on Veeam licensing.
5. Make sure all Veeam Backup & Replication servers that you want to connect to VAO 2.0 run Veeam Backup & Replication version 9.5 U4 (build number 9.5.4.2615) or later.

New Installation

This scenario implies that you uninstall VAO 1.0 completely, and then install and configure VAO 2.0 from scratch. 

This is the best option for those users who did not have Production sites in v1.0, and for those who can recreate all failover plans, perform initial configuration and recollect infrastructural data fast enough to avoid notable downtime.

1. Make sure that VAO agents are uninstalled from all connected standalone Veeam Backup & Replication servers in the VAO UI. For more information, see the Veeam Availability Orchestrator 2.0 User Guide, section Uninstalling VAO Agents. Make sure the “Force removal of Agent from VAO even if Veeam Backup & Replication server cannot be contacted” check box is not selected. If VAO is not able to access a Veeam Backup & Replication server, you can manually remove the required components from the server:
   • Open Control Panel.
   • Navigate to Programs and Features.
   • In the list of installed programs, select Veeam Orchestrator Agent and click Uninstall.
2. To perform installation, follow the instructions provided in the Veeam Availability Orchestrator 2.0 User Guide, section Deployment. 

Migration

This scenario implies that you have two side-by-side VAO deployments until the migration process is over, an old one (v1.0) and a new one (v2.0). Only one VAO deployment will be available for failover purposes, and you can expect a switchover period to involve downtime of all VAO services. This guide will help you minimize the switchover period the switchover period. 

The migration process includes three phases:

1. Preparation of VAO 2.0 system — includes installation and initial configuration of VAO 2.0, with no impact on the running 1.0 system.
2. Switchover from VAO 1.0 to 2.0 — during this phase, neither VAO 1.0 nor VAO 2.0 can execute orchestration plans. This can be considered downtime for the DR system.
3. Testing of new VAO 2.0 system and decommission of VAO 1.0.

 

• In VAO 2.0, clone the Default template. Open the new template in MS Word.
• In VAO 1.0, navigate to the template you want to copy Open the template in MS Word.
• Copy the text of VAO 1.0 template and paste it into the newly created 2.0 template.
• Save the 2.0 template.

Switchover Phase
 

• Open Control Panel.
• Navigate to Programs and Features.
• In the list of installed programs, select Veeam Orchestrator Agent and click Uninstall.

Testing and decommission of VAO 1.0 phase

Before decommissioning your VAO 1.0 installation, it is recommended that you make sure readiness checks and DataLab tests can complete successfully. If not, you can still revert to 1.0 (as described below).

Revert to VAO 1.0

• Open Control Panel.
• Navigate to Programs and Features.
• In the list of installed programs, select Veeam Orchestrator Agent and click Uninstall.