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

Upgrading Veeam Disaster Recovery Orchestrator

Upgrade to Orchestrator version 6.0 is supported from Orchestrator version 5.0 only. Upgrade from Orchestrator versions 4.0, 3.0 and 2.0 is not supported.

To learn how to manually migrate Orchestrator 1.0 deployment to version 2.0, see this Veeam KB article. To learn how to upgrade from Orchestrator 2.0 to Orchestrator 3.0, see the Veeam Availability Orchestrator 3.0 User Guide. To learn how to upgrade from Orchestrator 3.0 to Orchestrator 4.0, see the Veeam Availability Orchestrator 4.0 User Guide. To learn how to manually upgrade from Orchestrator 4.0 to Orchestrator 5.0, see the Veeam DIsaster Recovery Orchestrator 5.0 User Guide.

Upgrade Checklist

Check the following prerequisites before upgrading Orchestrator:

  1. Perform backup of all existing databases that are used to store data collected from Orchestrator, Veeam Backup & Replication and Veeam ONE, so that you can easily go back to the previous version in case of upgrade issues.
  2. Make sure there is enough space for upgrade of the Microsoft SQL Server configuration database. To calculate the required space, add at least 25% of free space to the size of the Microsoft SQL Server configuration database.

By default, the setup wizard installs Orchestrator with Microsoft SQL Server Express. Note that the maximum configuration database size for Microsoft SQL Server Express is 10 GB.

  1. Make sure there are no orchestration plans being tested or executed (that is, no plans are in the IN USE mode, HALTED state or any of the active states). For CDP plans, upgrade is available only for the following plan states: VERIFIED, NOT VERIFIED, COMMIT FAILBACK, UNDO FAILOVER and PERMANENT FAILOVER.

For the list of modes and states that different types of orchestration plans can acquire, see Running and Scheduling Replica Plans, Running and Scheduling CDP Replica Plans, Running and Scheduling Restore Plans, Running and Scheduling Storage Plans and Running and Scheduling Cloud Plans.

  1. Make sure there are no orchestration plans scheduled to run during upgrade. Otherwise, disable the configured schedule as described in sections Scheduling Failover, Scheduling CDP Failover, Scheduling Restore, Scheduling Storage Failover and Scheduling Cloud Restore.
  2. Make sure all active Orchestrator UI sessions are closed.

Performing Upgrade

To upgrade from Orchestrator 5.0 to Orchestrator 6.0, perform the following steps:

  1. Make sure the machine where Orchestrator will be installed meets the prerequisite conditions described in section System Requirements.
  2. Download the latest version of the product installation image from the Veeam downloads page. You can burn the downloaded image file to a CD/DVD or mount the installation image to the target machine using disk image emulation software.
  3. Start the setup wizard.
  4. Accept the license agreement.
  5. Review components to upgrade.
  6. Provide a license file.
  7. Perform system configuration check.
  8. Specify service account credentials.
  9. Review SQL server connection settings.
  10. Begin upgrade.
  11. Upgrade remote Veeam Backup & Replication servers to version 12.
  12. [Optional] Upgrade additional Veeam ONE Monitor Client instances to version 12.
  13. [Optional] Upgrade the Orchestrator UI if installed remotely.

 

Important

The embedded Veeam Backup & Replication and Veeam ONE servers are upgraded automatically, as part of the Orchestrator server upgrade process. DO NOT try to upgrade the embedded servers manually, by using the installation images of remote Veeam Backup & Replication and Veeam ONE solutions. Otherwise, the correct operation of the Orchestrator server cannot be guaranteed.