Vmware error: Failed to create lun snapshots

VMware Site Recovery Manager TestFailover task fails with the error: Failed to create lun snapshots


Symptoms

  • A TestFailover operation on VMware Site Recovery Manager (SRM) configured with IBM SAN Volume Controller (SVC) storage fails
  • You see the error:

    Non-fatal error information reported during execution of SRA: Failed to create lun snapshots.

  • The vmware-dr-X.log file on the VMware SRM server contains the errors:

    [#3] [ Thu Aug 27 10:45:05.628 testFailover trivia ] Acquiring lock...
    [#3] [ Thu Aug 27 10:45:05.753 testFailover trivia ] testFailover::ControllerConfigurationService
    [#3] [ Thu Aug 27 10:45:05.768 testFailover trivia ] testFailover::exposePaths()
    [#3] [ Thu Aug 27 10:45:05.784 testFailover trivia ] Attach Volumes returned: 4097
    [#3] [ Thu Aug 27 10:45:05.784 testFailover trivia ] Releasing lock...
    [#3] [ Thu Aug 27 10:45:05.784 testFailover Error ] 1 unmask failed
    [#3] [ Thu Aug 27 10:45:05.800 testFailover trivia ] testFailover::IBMTSSVC_HardwareIDStorageVolumeView
    [#3] [ Thu Aug 27 10:45:05.800 testFailover Error ] testFailover::createSVCFC(): 203
    [#3] [ Thu Aug 27 10:45:05.800 testFailover trivia ] Exit failoverTest End(): 203
    [#3] [ Thu Aug 27 10:45:05.800 testFailover trivia ] End testFailover::createSVCFC()
    [#3] [ Thu Aug 27 10:45:05.800 testFailover trivia ] End testFailover::getArrayTypeAndInfo()

    [2009-08-27 10:45:05.862 01836 error 'SecondarySanProvider'] testFailover's errors:
    java.lang.StringIndexOutOfBoundsException
    [#3] at java.lang.String.substring(String.java:1088)
    [#3] at testFailover.createSVCFC(testFailover.java:967)
    [#3] at testFailover.getArrayTypeAndInfo(testFailover.java:207)
    [#3] at testFailover.main(testFailover.java:163)
    .
    .
    [2009-08-27 10:45:05.862 01836 warning 'SecondarySanProvider'] Skipping replica LUN '0' without WWN, host numbers, or NFS name
    [2009-08-27 10:45:05.862 01836 info 'SecondarySanProvider'] Return code for testFailover: 203
    .
    .
    [2009-08-27 10:45:05.862 01836 error 'SecondarySanProvider'] No shadow LUNs found in testFailover/start output
    [2009-08-27 10:45:05.862 01836 verbose 'SecondarySanProvider'] Deleting lun snapshots
    .
    .

    [#3] [ Thu Aug 27 10:45:10.143 testFailover Error ] The CIMOM may not be functioning correctly.CIM_ERR_FAILED

    [2009-08-27 10:45:10.237 01836 error 'SecondarySanProvider'] testFailover's errors:
    org.sblim.wbem.cim.CIMException: CIM_ERR_FAILED; nested exception is:
    [#3] java.lang.NullPointerException
    [#3] at org.sblim.wbem.client.CIMClientXML.invokeMethod(CIMClientXML.java:778)
    [#3] at org.sblim.wbem.client.CIMClient.invokeMethod(CIMClient.java:2142)
    [#3] at testFailover.deleteSVCFC(testFailover.java:1218)
    [#3] at testFailover.getArrayTypeAndInfo(testFailover.java:210)
    [#3] at testFailover.main(testFailover.java:163)
    [#3] Caused by: java.lang.NullPointerException
    [#3] at org.sblim.wbem.xml.CIMXMLBuilderImpl.createINSTANCENAME(CIMXMLBuilderImpl.java:828)
    [#3] at org.sblim.wbem.xml.CIMClientXML_HelperImpl.invokeMethod_request(CIMClientXML_HelperImpl.java:552)
    [#3] at org.sblim.wbem.client.CIMClientXML.invokeMethod(CIMClientXML.java:734)
    [#3] ... 4 more
    .
    .
    [2009-08-27 10:45:10.237 01836 verbose 'BeginImageTest-Task'] Error set to (dr.san.fault.ExecutionError) {
    [#3] dynamicType = ,
    [#3] faultCause = (vmodl.MethodFault) null,
    [#3] errorMessage = "Failed to create lun snapshots",
    [#3] msg = "",
    [#3] }

Resolution

This issue occurs if a single IBM SVC Console is used to manage both the protected SVC cluster and the recovery SVC cluster.

To resolve this issue, when deploying VMware vCenter SRM with IBM SVC, use a unique SVC Console to manage the protected site and another unique SVC console to manage the recovery site. For more information, see IBM SVC documentation.
If you experience this issue, snapshots on the recovery site SVC may not be cleaned up. You may have to manually log in to the recovery SVC to remove the FlashCopy of the protected LUN.
  1. Log in to the recovery IBM SVC using the PuTTY utility on the SVC console.
  2. Unpresent the FlashCopy VDisk from the recovery site ESX with the command:

    svctask rmvdiskhostmap

  3. Stop the flashcopy between the replicated VDisk and the FlashCopy VDisk with the command:

    svctask stopfcmap

  4. Remove the FlashCopy map with the command:

    svctask rmfcmap

  5. Remove the FlashCopy VDisk with the command:

    svctask rmvdisk
Labels: , ,