My problem is to being able to do the quiesced snapshot of the operating system to be sure that it will be consistent.
I've read that KB but it only talks about microsoft iscsi and not of RDM LUN.
The strange things is that on my other 2 exchange server (that use microsoft iscsi) I'm able to do a quiesced fs snapshot without any problem.
On the machine when I get the problem it seems to be half a vmware/half a snapdrive problems.
When doing the snapshot on the machine with microsoft iscsi initiator i see that:
1) data onta vss add the source
2) snapshot lun are created on the storage bu snapdrive
3) lun are mapped by snapdrive
4) targetlun and snapshot are deleted by snapdrive
5) vm snapshot complete successfully
On the machine with RDM and without microsoft software iscsi i see:
1) data onta pvss add the source
2) snapshot lun are created on the storage bu snapdrive
3) lun are mapped by snapdrive
here there are 15 minutes of wait
4) i start to get errr by vss provider:
-VSS 12362 - A Shadow Copy LUN was not detected in the system and did not arrive.
5)snapdrive report targetlun delete succeded
6) snapdrive report an error in the deletesnapshot:
-snapdrive eventid 245:
DeleteSnapShot operation failed.
Storage System Name = storage1
lunPath = /vol/exchlab_2007/exchlab2007
Snapshot copy Name = {69f15de6-e63e-4b25-907f-35202bf40fa4}
Error code = 0xc004030b
Error description = An attempt to delete Snapshot copy '{69f15de6-e63e-4b25-907f-35202bf40fa4}' of the 'exchlab_2007' volume failed on the storage system 'storage1'. Error code: 16. Error description: LUN clone.
So in my understanding it seems that snapdrive in this case in not able to complete the point 3 to map the lun or is not able to see the snapshot of the VM.
It would be great if snapdrive will not even try to snapshot those disks when the VSS provider is invoked for a vm quiesced snapshot but it try and fail in the case of RDM lun (instead it works out good in the case of microsoft iscsi initiator lun).
We are trying to move to external RDM for DR using SD6.2/SM6.0 to backup/mirror exchange data, SMVI 2.0 to backup/mirror the machine and SRM 4 (with the 1.4.3 netapp adapter when it will be out) to restart the environment in DR site but with those error our exchange server will not have the OS disk quiesced/consistent.
Regards
Francesco
