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

VMware Validated Design 4.3 vRealize Operations Disaster Recovery Failover (67278)

Last Updated: 7/14/2020Categories: How toTotal Views: 2300Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Purpose

This article provides recommend steps to perform a disaster recovery failover and failback of vRealize Operations Manager from when vRealize Operations Manager remote collectors are inaccessible.

Resolution

Note: The FQDNs and node names below are examples.  Replace the FQDNs and IPs as needed.

After you perform disaster recovery, when vRealize Operations Manager remote collectors in Region A are permanently inaccessible, you must remove the remote collectors using the admin UI.

Failover to Region B:
Perform the following steps as part of Post-Failover Configuration of the SDDC Management Applications:

Delete the inaccessible remote collectors from vRealize Operation using the administrative UI and vSphere inventory.

Log in to vRealize Operations Manager Primary Node's admin UI at https://vrops01svr01a.rainpole.local/admin as the local admin user.

Select the inaccessible remote collector and click Remove Node.

Check I understand that performing this action will remove the selected Node from the Cluster and click Yes.

Repeat steps 2-3 for any other inaccessible remote collectors.

Delete the cross-region environment card and re-import the cross-region environment

Follow the procedures to delete and re-import the cross-region environment using the documentation below:

Delete the Cross-Region Environment in vRealize Suite Lifecycle Manager

Import the Cross-Region Environment in vRealize Suite Lifecycle Manager

Redeploy and connect the remote collectors after the cluster is moved back to Region A as part of failback after Region A restoration

Log in to the vSphere Web Client at https://sfo01m01vc01.sfo01.rainpole.local/vsphere-client as [email-masked].

Navigate to Home > VMs and Templates.

Navigate to the sfo01m01vc01.sfo01.rainpole.local vCenter Server and expand the sfo01-m01dc datacenter.

Click the Virtual Machines tab.

Right-click sfo01vrops01a, select Delete from disk and select Yes to confirm the deletion.

Repeat the above step for the sfo01vrops01b remote collector.

Follow Deploy vRealize Operations Manager Nodes Using vRealize Suite Lifecycle Manager in Region B to add the remote collectors.  Use the same instruction to redeploy sfo01vrops01a and sfo01vrops01b remote collectors in Region A; use appropriate configurations that are relevant to Region A remote collectors.

Reset the collector group

Log in to vRealize Operations Manager Primary Node's admin UI at https://vrops01svr01a.rainpole.local/admin as the local admin user.

Navigate to Administration > Management > Collector Groups.

Select sfo01-remote-collectors and click Edit.

Select sfo01vrops01a and sfo01vrops01b and click save

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
「vpxd firstboot」の実行中に 6.5 から 6.7 への vCenter Server Appliance アップグレードが失敗する (76970)

KB
•
VMware Smart Assurance 10.0.x: MongoDB、Kafka、Elastic Search、Redis をインストールするスクリプト (70718)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Validated Design for Software-Defined Data Center (SDDC) 4.3.x

VMware Validated Design for Software-Defined Data Center (SDDC)

Take Our Survey

Support Assistant