Tuesday 3 March 2015

Unable to Perform Test Recovery via SRM : Failed to create Lun snapshots

Issue Definition: Was unable to perform test recovery via SRM

- Checked via the Storage monitor and found the replication was working.
- Tried to increase the timeout for the Lun snapshot and performed the test recovery again : did not work.


Log Snippet: Dr.Logs

- Checked the SRM recovery log file and found the below error messages :
===================================================================

[2011-09-29 18:02:26.098 02276 trivia 'SecondarySanProvider'] testFailover's output:
D:/Program Files (x86)/VMware/VMware vCenter Site Recovery Manager/scripts/SAN/IBMSVC[ Thu Sep 29 18:02:22.825 testFailover Info ] SRA Version 1.20.71310
[#4] [ Thu Sep 29 18:02:22.857 testFailover Info ] Preconfig option setting ... false
[#4] [ Thu Sep 29 18:02:23.218 testFailover Error ] No valid WWPN found in the input...
[#4] [ Thu Sep 29 18:02:23.218 testFailover trivia ] Begin testFailover()
[#4] [ Thu Sep 29 18:02:23.224 testFailover trivia ] End testFailover()
[#4] [ Thu Sep 29 18:02:23.224 testFailover trivia ] testFailover::stop
[#4] [ Thu Sep 29 18:02:23.224 testFailover trivia ] Begin testFailover::getArrayTypeAndInfo()
[#4] [ Thu Sep 29 18:02:23.224 testFailover trivia ] testFailover::CIM_ObjectManager
[#4] [ Thu Sep 29 18:02:23.771 testFailover trivia ] Begin testFailover::deleteSVCFC()
[#4] [ Thu Sep 29 18:02:23.771 testFailover trivia ] Begin testFailover::getSVCSCS()
[#4] [ Thu Sep 29 18:02:23.771 testFailover trivia ] testFailover::IBMTSSVC_StorageConfigurationService
[#4] [ Thu Sep 29 18:02:23.802 testFailover trivia ] End testFailover::getSVCSCS()
[#4] [ Thu Sep 29 18:02:23.802 testFailover trivia ] testFailover::IBMTSSVC_RemoteStorageSynchronized
[#4] [ Thu Sep 29 18:02:24.843 testFailover trivia ] testFailover::IBMTSSVC_Cluster
[#4] [ Thu Sep 29 18:02:24.969 testFailover trivia ] testFailover::IBMTSSVC_LocalStorageSynchronized
[#4] [ Thu Sep 29 18:02:25.61 testFailover trivia ] testFailover::IBMTSSVC_SynchronizedSet
[#4] [ Thu Sep 29 18:02:25.204 testFailover trivia ] testFailover::IBMTSSVC_StorageVolume
[#4] [ Thu Sep 29 18:02:25.961 testFailover trivia ] testFailover::IBMTSSVC_HardwareIDStorageVolumeView
[#4] [ Thu Sep 29 18:02:26.58 testFailover Warning ] No snapshots to cleanup

[2011-09-29 18:02:26.099 02276 info 'SecondarySanProvider'] testFailover exited with exit code 0
[2011-09-29 18:02:26.099 02276 trivia 'SecondarySanProvider'] 'testFailover' returned <?xml version="1.0" encoding="ISO-8859-1"?>
[#4] <Response>
[#4] <ReturnCode>0</ReturnCode>
[#4] </Response>
[#4]
[2011-09-29 18:02:26.099 02276 info 'SecondarySanProvider'] Return code for testFailover: 0
[2011-09-29 18:02:26.099 02276 verbose 'SecondarySanProvider'] Removed dependent 'shadow-group-171743' from array 'array-56521'
[2011-09-29 18:02:26.100 02276 trivia 'SecondarySanProvider'] 'Prepare storage for group 'shadow-group-171743' for recovery' took 10.579 seconds
[2011-09-29 18:02:26.100 02276 verbose 'PropertyProvider'] RecordOp ASSIGN: info.error, BeginImageTest-400
[2011-09-29 18:02:26.100 02276 verbose 'BeginImageTest-Task'] Error set to (dr.san.fault.ExecutionError) {
[#4] dynamicType = <unset>,
[#4] faultCause = (vmodl.MethodFault) null,
[#4] errorMessage = "Failed to create lun snapshots",
[#4] msg = "",
[#4] }

Checks Performed: 
===================


- Error was related to the Zoning : No valid WWPN found in the input.
- Next step to check the Zoning
- Found multiple errors on the Storage monitor.

Action Plan :
===========
- Would be to take a manual snapshot of the consistency group.


**After checking that the manual snapshot of the consistency group did not work and involved storage vendor for further assistance.