VMware Cloud Community
76dragon
Enthusiast
Enthusiast

Celerra Failed to create snapshot luns

Hi Guys.

Ive had 2 x NS Celerra's setup for quite some time now and SMR has stopped working for some reason. Licensing is not the issue.

The error in the SRM logs is as such.

2009-05-11 15:27:59.216 'RootStepList-49071-Task' 2812 info State set to error

2009-05-11 15:27:59.216 'RootStepList-49071-Task' 2812 info Not Starting Tasks All Tasks Complete

2009-05-11 15:27:59.216 'RSStorageOperationList-49261-Task' 2812 verbose Task destroyed

2009-05-11 15:27:59.216 'RecoveryContext-33-Task' 2292 verbose Progress advanced to 100

2009-05-11 15:27:59.216 'RootStepList-49071' 2292 info SetTaskComplete root

2009-05-11 15:27:59.216 'RootStepList-49071' 2292 info SetRuntimeStatus for RootStepList-49071 from cancelling to error

2009-05-11 15:27:59.216 'RootStepList-49071' 2292 info RuntimeInfoError (dr.fault.MultipleFault) {

dynamicType = <unset>,

faults = (vmodl.MethodFault) [

(dr.san.fault.ExecutionError) {

dynamicType = <unset>,

errorMessage = "Failed to create lun snapshots",

msg = ""

}

],

msg = ""

}

The problem im sure is on the Array end as the error on the Celerra shows;

NBS: 3: BlkSrvConfigID::SnapCreate failed for /fs49_T3_LUN0_CK200082400875_0000/fs49_T3_LUN0_CK20 0082400875_0000, NBS_EDSTLUN

The file system the iSCSI lun resides in has tones of space is is not related to an issue ive seen before where it cant create the snapshot because the FS is full with other checkpoints.

I also see the following errors in SRM logs.

dynamicType = <unset>,

faults = (vmodl.MethodFault) [

(dr.fault.InternalError) {

dynamicType = <unset>,

reason = "Failed to create group image: unknown exception",

msg = ""

}

],

msg = ""

Any Celerra guru's out in the SRM community have any ideas ?

Thanks

0 Kudos
1 Reply
jbloo2
Enthusiast
Enthusiast

Hi 76dragon - I would suggest uploading the SRM log which includes the output of the Celerra adapter from when this occurred as it may include additional information that would be helpful in debugging this further, as the message on the Celerra array doesn't seem to be sufficient. You can find the SRM logs in c:\documents and settings\all users\application data\vmware\vmware site recovery manager\logs