we have a little problem with SME 6.1.0 (1434) and SD 7.1 in conjunction with VMWare 5.5.
The environment of our customers: VMWare 5.5 inclusive iSCSI service Exchange 2010 DAG 3x and 2x CAS SME runs on DAG3 DAG3 server has connected vmdk boot LUN and 2 RDM LUN via VMWare iSCSI
To our problem: SME job runs so far without spec except the backup verification brings a SD error:
SME BackupJob LOG [10: 00: 42,573] BackupVerification job of JobID 5902 starts to run on server NAME [10: 00: 42,573] The destination volume of the source logical disk C: \ Exchange Data \ db01 \ FlexClone State is Success and SnapMirror State is Unknown. [10: 00: 49,576] Mounting Snapshot [exchsnap__NAME_04-17-2015_10.00.13__daily] for LUN C: \ Exchange Data \ db01 \ created from computer NAME [10: 00: 49,576] Mount point directory [C: \ Exchange Data] [10: 00: 51,105] snapshot will be mounted on subdirectory [MPDisk576] [10: 01: 40,582] [SnapDrive Error]: Error in fetching vmfs datastores. (SnapDrive Error Code: 0xc00404c3) [10: 01: 40,582] Unable to mount snapshot, abort verification. [10: 01: 40,582] [SnapDrive Error]: Error in fetching vmfs datastores. [10: 01: 40,582] BackupVerification job of JobID = 5902 is finished with status Failed. [10: 01: 40,582] [SnapDrive Error]: Error in fetching vmfs datastores.
"Error in fetching vmfs datastores" is logged by SnapDrive when unable to gather the list of the Datastores from the Vcenter Server, which is the first thing SnapDrive does, when creating a RDM lun (like in your case, when verifying the lun inside the snapshot).
You are probably having a communication issue between SnapDrive and Vcenter Server:
You need to log a case or check yourself the Snapdrive VirtualizationAPI log inside the snapdrive installation directory, for more clues.
That log reports all soap https calls betweeen snapdrive and vcenter.
You could also try to workaround by forcing SnapDrive to use the guest SW iscsi initiator for verification purposes, but than you are not fixing a more important issue. You must address this or else soon or later you will have this error when creating an RDM lun with SnapDrive.