Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Manual Synchronization of the Embedded vRO Cluster (59598)

Last Updated: 7/15/2020Categories: How toTotal Views: 3764Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

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.

Purpose

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.

Resolution

Please ensure that a backup is taken prior to completing this procedure.

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

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.

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

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Aria Automation Orchestrator

Related Versions:

VMware vRealize Orchestrator 7.x

Take Our Survey

Support Assistant