You can migrate your cluster of vRealize Orchestrator 6.x Virtual Appliances to a cluster of vRealize Orchestrator 7.3 instances.
Prerequisites
Set up a load balancer to distribute traffic among multiple instances of vRealize Orchestrator. For more information, see vRealize Orchestrator Load Balancing.
Deploy and configure an Orchestrator node on the target version. See Configuring a Standalone Orchestrator Sever.
If the source Orchestrator uses a SHA1 package-signing certificate, make sure to regenerate the certificate using a stronger signing algorithm. The recommended signing algorithm is SHA2.
Stop the Orchestrator server service of the source Orchestrator instances.
Back up the database, including the database schema, of the external Orchestrator.
Note:If you plan to use the source Orchestrator environment until the new one is fully configured, create a copy of the source database. Otherwise, you can configure the target Orchestrator to use the same database but in that case the source Orchestrator environment will no longer work because the database schema is upgraded to the version of the target Orchestrator.
Procedure
Results
You successfully migrated a cluster of vRealize Orchestrator 6.x Virtual Appliances to an Orchestrator cluster 7.3.
What to do next
On the Orchestrator Cluster Management page, make sure that the Active Configuration Fingerprint and the Pending Configuration Fingerprint strings on all nodes in the cluster match.
Note:You might need to refresh the page several times until the two strings match.
Verify that the vRealize Orchestrator cluster is configured properly by opening the Validate Configuration page in Control Center.
Log in to the Orchestrator client and verify whether the configurations of all installed plug-ins are correct.