Reinstalling Orchestrator Using Existing Databases

In some cases, you may need to migrate the Orchestrator server to another machine or reinstall it using existing databases. To do that, follow the instructions provided in this section.

Step 1. Back Up Existing Databases

Before you reinstall Orchestrator, you must create backups of databases used to store data collected from Orchestrator, Veeam Backup & Replication and Veeam ONE, which were previously installed with the Orchestrator server.

Step 2. Restore Backed-Up Databases

Restore the backed-up Orchestrator, Veeam Backup & Replication and Veeam ONE databases to a new local or remote Microsoft SQL Server instance.

Step 3. Install Veeam Recovery Orchestrator

Run the Orchestrator setup wizard and follow the instructions provided in section Deploying Veeam Recovery Orchestrator.

At the SQL Server Settings step of the wizard, browse to the restored Orchestrator database and specify names for new Veeam Backup & Replication and Veeam ONE databases.

Step 4. Reinstall Veeam ONE and Veeam Backup & Replication

As soon as the Orchestrator installation process completes:

1. Open the Services snap-in and stop the Veeam Orchestrator Server Service, Veeam Orchestrator ONE Integration Service and Veeam Orchestrator Agent for Backup service.
2. Reconfigure Veeam ONE and Veeam Backup & Replication servers to use old databases instead of new ones created during Orchestrator installation.

For more information, see these Veeam KB articles: Moving Veeam ONE database to a different SQL Server and How to move the Veeam Backup & Replication software to another server.

3. Start the Veeam Orchestrator Server Service, Veeam Orchestrator ONE Integration Service and Veeam Orchestrator Agent for Backup service.

Step 5. Additional Configuration

Depending on the new database location, you will have to perform a number of additional actions.

Installing Orchestrator on the same machine

If you have performed installation on the same machine that was used to run Orchestrator earlier, no additional configuration is required.

Installing Orchestrator on a new machine with the same name

If you have performed installation on a new machine with the same name as the machine that was used to run Orchestrator earlier, do the following.

1. Open the Orchestrator UI and switch to the Administration page.
2. Navigate to Credentials.

Modify all manually added credentials managed by the Orchestrator server.

1. Select a credential and click Edit.
2. In the Edit Credentials window, enter a password for the credential.
3. Repeat the step for each manually added credential.

3. Navigate to Orchestrator Agents and make sure that all Orchestrator agents previously installed on the server have the Healthy status.
4. Navigate to VMware and make sure that all VMware servers previously connected to the server have the Connected status.
5. Navigate to Storage and make sure that all storage systems previously connected to the server have the Connected status.

6. [This step applies only if you have previously connected an SMTP server and enabled authorization]

Navigate to Mail.

1. Click Edit.
2. In the SMTP Server window, enter a password required for SMTP server authentication.

Installing Orchestrator on a new machine with a new name

If you have performed installation on a new machine with a new name, follow the instructions provided in steps 1–6. No additional actions are required.