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

Recovery after a failed reprotect (55007)

Last Updated: 6/1/2018Categories: How toTotal Views: 5553Language:
Chinese (Simplified)JapaneseEnglish

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

Array based replication.

Recovery Plan shows as interrupted.

Reprotect incomplete VMs showing as Recovery in progress.

Failover completed at the array level.

Cause

This issue is caused when SRM & SRA are out of sync with each other.

Resolution

Confirm the flow of replication has been restored in the correct direction. If the flow is in the correct direction do the following in this order.

Run Discover Array Pairs.

Try running Recovery/Reprotect again.

If Recovery/Reprotect fails reboot SRM servers and vCenter.

Try running Recovery/Reprotect again.

If Recovery/Reprotect fails destroy the protection group & recovery plan & recreate with the below steps:

a) Remove protection from all VMs associated with the protection group.

In the vSphere Web Client, click Site Recovery > Protection Groups.

​Select an array-based replication or a vSphere Replication protection group and select Related Objects > Virtual Machines.

Right-click a virtual machine and select Remove Protection.

Click Yes to confirm the removal of protection from the virtual machine.

b) Remove the placeholder VMs from inventory.

In the vSphere Web Client, locate the VM at the target site.

Right-click the VM and select Delete From Disk.

Delete the protection group.

In the vSphere Web Client, click Site Recovery > Protection Groups.

Right-click the protection group to delete, and select Delete Protection Group.

d) Delete the recovery plan

In the vSphere Web Client, click Site Recovery > Recovery Plans.

Right-click the recovery plan to delete, and select Delete Recovery Plan.

Recreate protection group.

In the vSphere Web Client, click Site Recovery > Protection Groups.

Click on Create Protection Group and complete the wizard.

f) Recreate recovery plan

In the vSphere Web Client, click Site Recovery > Recovery Plans.

Click on Create Recovery Plan and complete the wizard

If you get an error "Can't remove protection from VMs due to error Group <protection group name> is currently used by a recovery plan" then SRM will need to be redeployed as SRM DB and SRM are out of sync on VMs locations.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)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

Related Versions:

VMware vCenter Site Recovery Manager 8.x

VMware vCenter Site Recovery Manager 6.5.x

VMware vCenter Site Recovery Manager 6.0.x

Take Our Survey

Support Assistant