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

Unable to break site pairing from OnPrem SRM on deactivating DRaaS on VMConAWS (57774)

Last Updated: 9/4/2018Categories: How toTotal Views: 4084Language:
JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

After Deactivating DRaaS for SDDC with an active SRM pairing, you are unable to break pairing from your on-prem SRM UI

Cause

Known issue is that SRM pairings need to be broken, before one of the SRM instances in the pairing is uninstalled. If SRM instance is uninstalled without its pairing is broken, an orphaned pairing remains on the other SRM instances. An orphaned pairings cannot be removed by the SRM interface. SRM with such pairing needs to be re-installed with a clean DB.

The VMC Deactivate DR workflow doesn’t delete for activate SRM pairing. On users’ consent Deactivate DR directly deletes the SRM/VR appliances from the VMC SDDC. In this scenario is possible orphaned pairing or remain on the on-prem SRM instance.

The clean uninstall process is documented in the VMware Site Recovery Installation and Configuration - VMware Site Recovery guide under  "Uninstall Site Recovery Manager on the on-premises site"

Resolution

To bring the OnPrem site to clean state:

For VR - you can:

1. force stop the leftover replications
2. force disconnect the leftover pairing.
Alternatively - you can reset VRMS DB and on next startup of VRMS it will remove the stale outgoing replications -                                         open https://vr_address:5480/, click on "Reset embedded db" and do "Save and restart" with SSO Admin password.

For SRM the only option is to:

1. De-install SRM server.
2. De-install SRM embedded DB.
3. Re-install SRM embedded DB and SRM server.

Refer: Unable to modify/repair/uninstall SRM service (56354)

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
JapaneseEnglish

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Site Recovery Manager

VMware Cloud on AWS

Related Versions:

VMware vCenter Site Recovery Manager 8.x

VMware vCenter Site Recovery Manager 8.1.x

Take Our Survey

Support Assistant