You can migrate a single node vRealize Orchestrator instance that is embedded in vRealize Automation 7.x to an embedded vRealize Orchestrator 8.x deployment.
The migration transfers an embedded vRealize Orchestrator 7.x configuration to your vRealize Orchestrator 8.x environment. The migration involves overwriting all existing elements in your vRealize Orchestrator 8.x environment.
- Migration is supported for embedded vRealize Orchestrator 7.3 or later.
- Back up the target vRealize Automation environment.
- Verify that SSH access is enabled on the source vRealize Automation instance and target vRealize Automation environment.
- Verify that the source vRealize Automation database is accessible from the target vRealize Automation environment.
- Log in to the vRealize Orchestrator appliance command line of your target environment over SSH as root.
- To start the migration, run the vro-migrate script.
- Follow the command prompts to provide the fully qualified domain name (FQDN) and credentials of the source vRealize Orchestrator instance.
- (Optional) To follow the migration progress, access the migration log:
The migration process begins. You receive a notification on the target vRealize Orchestrator appliance when the migration finishes.
- Log in to your target vRealize Orchestrator appliance command line over a separate SSH session as root.
- Run the tail -f /var/log/vro-migration.log command.
- (Optional) After the migration process finishes, log in to the source vRealize Orchestrator appliance and restart the vco-server and vco-configurator services.
Note: Restarting the vRealize Orchestrator services ensures that your 7.x deployment is accessible after migration. After the restart, navigate to the Services tab in the source vRealize Automation, and verify that the vRealize Orchestrator services are registered.
- Log in to the target vRealize Automation appliance over SSH, run kubectl get pods -n prelude, and verify that the vRealize Orchestrator appliance reports 3/3.
Note: You might have to wait for up to 20 minutes before you run the kubectl get pods -n prelude command.
- Verify that vRealize Orchestrator is accessible in the target vRealize Automation environment.