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.
Restore the backed-up Orchestrator, Veeam Backup & Replication and Veeam ONE databases to a new local or remote Microsoft SQL Server instance.
It is required that the restored databases are located on the same Microsoft SQL Server instance and have the same names as the previously installed databases.
Step 3. Install Veeam Disaster Recovery Orchestrator
Run the Orchestrator setup wizard and follow the instructions provided in section Deploying Veeam Disaster Recovery Orchestrator.
At the SQL Server Database step of the wizard, browse to the restored Orchestrator database and specify names for new Veeam Backup & Replication and Veeam ONE databases.
Orchestrator reinstallation process does not involve the Veeam Backup & Replication and Veeam ONE databases restored at Step 2. Restore Backed-Up Databases.
To allow Orchestrator to use the restored databases, you must perform reconfiguration of Veeam ONE and Veeam Backup & Replication servers. For more information, see Step 4. Reinstall Veeam ONE and Veeam Backup & Replication.
As soon as the Orchestrator installation process completes:
- Open the Services snap-in and stop the Veeam Orchestrator Server Service, Veeam Orchestrator ONE Integration Service and Veeam Orchestrator Agent for Backup service.
- 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.
- 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.
- Open the Orchestrator UI and switch to the Administration page.
- Navigate to Orchestrator Agents. All Orchestrator agents previously installed on the server will have the Repair Required status.
- Select an agent and click Repair.
- In the Repair Orchestrator Agent window, enter passwords required for the remote access and service credentials.
- Repeat the step for each agent with the Repair Required status.
- Navigate to VMware vCenter Servers. All VMware servers previously connected to the server will have the Disconnected status.
- Select a vCenter Server and click Edit.
- In the Edit VMware vCenter Server window, enter a password required to connect to the server.
- Repeat the step for each VMware server with the Disconnected status.
- Navigate to Scope Inclusions > Credentials.
Modify all manually added credentials managed by the Orchestrator server.
- Select a credential and click Edit.
- In the Edit Orchestrator Credential window, enter a password for the credential.
- Repeat the step for each manually added credential.
All credentials collected from standalone Veeam Backup & Replication servers will be automatically updated as soon as Orchestrator agents installed on the servers connect to the Orchestrator server.
- [This step applies only if you have previously connected an SMTP server and enabled authorization]
Navigate to SMTP Server.
- Click Edit.
- 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–5. No additional actions are required.
To make sure all the configuration changes are correct, after you perform the required actions, generate the Plan Readiness Check Report for each Orchestrator plan. For more information on the report, see Running Plan Readiness Check.