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

Delay in discovery during SRM reprotect due to cosmetic error message (56945)

Last Updated: 12/7/2018Categories: InformationalTotal Views: 3120Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Since SRM does not wait for storage side device discovery to complete before it triggers sync request during Reprotect operation, in environments with large number of storage devices this process can result in a harmless/cosmetic error message caused by a delay in device discovery process.

You see an error message similar to:

Error - Failed to sync data on replica devices. A specified parameter was not correct: deviceGroup"

Cause

Sync task after Reprotect operation does not serve any purpose except to kick off first sync between sites after Reprotect task is done.

SRM's Reprotect and Failover functionalities are NOT impacted in any way by the observed error message. It is completely harmless for the Reprotect and subsequent Failover operations.

One cannot initialize another Reprotect task after seeing this error event, because previous Reprotect task has already been successful and cannot be repeated.

Failover operation, when triggered, will initiate its own sync task (regardless of the status of the one triggered as part of reprotect operation) and ensure that all data is replicated to the other site before continuing with the process.

This behavior is not specific to any storage model/vendor in particular and depends solely on time required for storage side to discover device operation to be completed.

Resolution

This error is purely cosmetic and harmless in nature, which has no impact to the SRM, SRA or Storage Array functionality.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

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

Take Our Survey

Support Assistant