Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

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

Destination Site Recovery Manager service crashes when performing a failover with array based replication (SRM 6.1.1) (58481)

Last Updated: 9/18/2018Categories: TroubleshootingTotal Views: 6457Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

While performing an Array Based Replication recovery plan, you see these symptoms:

The Site Recovery Manager service suddenly experiences a panic/crash.

In the Site Recovery Manager logs, you see entries similar to:

T07:10:20.143-05:00 [11512 verbose 'Storage' opID=5659a390:64df:ab86:3a5a] Retrieved FC HBA 'vmhba2' for host 'host-1560'
T07:10:20.143-05:00 [11512 verbose 'Storage' opID=5659a390:64df:ab86:3a5a] Ignoring HBA 'vmhba0' which is neither FC nor iSCSI for host 'host-1561'
T07:10:20.143-05:00 [11512 verbose 'Storage' opID=5659a390:64df:ab86:3a5a] Retrieved FC HBA 'vmhba1' for host 'host-1561'
T07:10:20.143-05:00 [11512 verbose 'Storage' opID=5659a390:64df:ab86:3a5a] Retrieved FC HBA 'vmhba2' for host 'host-1561'
T07:10:20.143-05:00 [11512 verbose 'Storage' opID=5659a390:64df:ab86:3a5a] Ignoring HBA 'vmhba0' which is neither FC nor iSCSI for host 'host-1562'
T07:10:20.143-05:00 [11512 verbose 'Storage' opID=5659a390:64df:ab86:3a5a] Retrieved FC HBA 'vmhba1' for host 'host-1562'
T07:10:20.143-05:00 [11512 verbose 'Storage' opID=5659a390:64df:ab86:3a5a] Retrieved FC HBA 'vmhba2' for host 'host-1562'
T07:10:20.143-05:00 [11512 verbose 'Storage' opID=5659a390:64df:ab86:3a5a] Ignoring HBA 'vmhba0' which is neither FC nor iSCSI for host 'host-1563'
T07:10:20.143-05:00 [11512 verbose 'Storage' opID=5659a390:64df:ab86:3a5a] Retrieved FC HBA 'vmhba1' for host 'host-1563'
T07:10:20.143-05:00 [11512 verbose 'Storage' opID=5659a390:64df:ab86:3a5a] Retrieved FC HBA 'vmhba2' for host 'host-1563'
T07:10:20.143-05:00 [11512 verbose 'Storage' opID=5659a390:64df:ab86:3a5a] Ignoring HBA 'vmhba0' which is neither FC nor iSCSI for host 'host-1564'
T07:10:20.143-05:00 [11512 verbose 'Storage' opID=5659a390:64df:ab86:3a5a] Retrieved FC HBA 'vmhba1' for host 'host-1564'
T07:10:20.143-05:00 [11512 verbose 'Storage' opID=5659a390:64df:ab86:3a5a] Retrieved FC HBA 'vmhba2' for host 'host-1564'
T07:10:22.862-05:00 [10180 verbose 'RecoveryManagerContext'] Context queue under threshold of 15 items with 0.
T07:10:22.877-05:00 [12056 info 'Recovery' opID=394be2ba] GetTask called for plan: dr.recovery.RecoveryPlan['5f951503-b260-4ae6-a5f9-b7b0a5d9b66c']
T07:10:22.877-05:00 [00792 panic 'Default' opID=5659a390:64df:ab86:3a5a]
--> Panic: Win32 exception: Access Violation (0xc0000005)
--> Read (0) at address 0000000000000038
--> rip: 000000000eaee77e rsp: 000000001cafe1a0 rbp: 000000001e596650
--> rax: 0000000000000001 rbx: 0000000000000000 rcx: 0000000014989000
--> rdx: 0000000000000064 rdi: 000000002379e240 rsi: 000000002379ea20
--> r8: 0000000008cf3240 r9: 0000000000008000 r10: 732e6769666e6f63
--> r11: 000000001cafe198 r12: 0000000000000000 r13: 000000000cb17268
--> r14: 000000001e0f8738 r15: 0000000000000000
--> Backtrace:
--> [backtrace begin] product: VMware vCenter Site Recovery Manager, version: 6.1.1, build: build-4535903, tag: -
--> backtrace[00] vmacore.dll[0x001BF51A]
--> backtrace[01] vmacore.dll[0x0005D88F]
--> backtrace[02] vmacore.dll[0x0005E9DE]
--> backtrace[03] vmacore.dll[0x001D7A55]
--> backtrace[04] vmacore.dll[0x001D7B96]
--> backtrace[05] vmacore.dll[0x001DB1C6]
--> backtrace[06] MSVCR90.dll[0x00045129]

In the /var/log/vmkernel.log file on one of the ESXi host on the destination site, you see entries similar to:

T20:51:21.955Z: [scsiCorrelator] 47527766173478us: [esx.problem.storage.connectivity.lost] Lost connectivity to storage device eui.XXXXXXXXXXXXXXXX. Path vmhbaX:CX:TX:LX is down. Affected datastores: Unknown.
T20:51:21.955Z: [scsiCorrelator] 47527069820606us: [vob.scsi.scsipath.pathstate.dead] scsiPath vmhbaX:CX:TX:LX changed state from on.

Cause

This issue occurs due to an an ESXi host on the destination site responding with a NULL value during an HBA rescans that are performed during the running of the Recovery Plan.

For example, if a device involved with the Recovery Plan appears as an APD volume on one of the Disaster Recovery site hosts, this could result in a NULL response which results in the crash.

Impact / Risks

This impacts the ability to failover Recover Plans and thus vSphere environments in a disaster or planned failover scenario.

Resolution

This issue is resolved in:

​VMware Site Recovery Manager 6.1.2, available at VMware Downloads.

VMware Site Recovery Manager 6.5.1, available at VMware Downloads.

VMware Site Recovery Manager 8.1.x, available at VMware Downloads.

Workaround

To work around this issue if you do not want to upgrade, before performing your failover plan, ensure that no storage devices on the Disaster Recovery site are in an All Paths Down state.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
Preguntas frecuentes sobre VMware vSphere 5. x para VMFS-5 (2003813)

KB
•
有关适用于 VMFS-5 的 VMware vSphere 5.x 的常见问题 (2003813)

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:

Take Our Survey

Support Assistant