Manual Synchronization of the Embedded vRO Cluster
Article ID: 319601
Updated On:
Products
VMware Aria Suite
Issue/Introduction
In vRealize Orchestrator 7.2, it was possible to synchronize the vRealize Orchestrator nodes manually via a hidden option following "A configuration synchronization is required" error in clustered vRO nodes.
This procedure provides the same functionality for vRealize Orchestrator 7.3 where this hidden option has been removed and acts as an alternative to rejoining the node to the cluster.
Symptoms:
One of the embedded vRealize Orchestrator nodes is showing out of sync within a vRealize Orchestrator cluster.
Please note that this procedure is an alternative to the preferred vRealize Automation join node mechanism, where the out of sync node is rejoined to the primary vRealize Automation node which can be completed through the VAMI interface.
This procedure provides the same functionality for vRealize Orchestrator 7.3 where this hidden option has been removed and acts as an alternative to rejoining the node to the cluster.
Symptoms:
One of the embedded vRealize Orchestrator nodes is showing out of sync within a vRealize Orchestrator cluster.
Please note that this procedure is an alternative to the preferred vRealize Automation join node mechanism, where the out of sync node is rejoined to the primary vRealize Automation node which can be completed through the VAMI interface.
Environment
VMware vRealize Orchestrator 7.x
Resolution
Please ensure that a backup is taken prior to completing this procedure.
Note: Replace path-to-archive with the location on the copied configuration from step 3.
- Stop the vRealize Orchestrator Server and Control Center on each node with the following command:
service vco-server stop; service vco-configurator stop
- On the primary execute the following commands to clear the database tables:
su postgres
psql
\c vcac
delete from vmo_vroconfiguration;
delete from vmo_vroconfigurationhistory;
\q
exit
psql
\c vcac
delete from vmo_vroconfiguration;
delete from vmo_vroconfigurationhistory;
\q
exit
- Export the configuration from the primary node:
/usr/lib/vco/tools/configuration-cli/bin/vro-configure.sh export --skipPluginConfigurations --skipLicense --skipTrustStore --path path-to-archive
Note: Replace path-to-archive with the desired path to save the exported configuration.
Note: Replace path-to-archive with the desired path to save the exported configuration.
- Copy the exported archive on each of the other nodes using an SCP utility.
- Import the exported archive on each of the other nodes
- chown 777 /tmp/archive.zip
- chmod vco:vco /tmp/archive.zip
- /usr/lib/vco/tools/configuration-cli/bin/vro-configure.sh import --type sync --path /tmp/archive.zip
Note: Replace path-to-archive with the location on the copied configuration from step 3.
- Start vRealize Orchestrator Server and Control Center on each node:
service vco-server start; service vco-configurator start
Feedback
Yes
No
Powered by
