Have you performed consistent backups with SME and then mirrored the correct snapshots over to the destaination? Ideally you did this with SnapManager, so this would ensure consistency.
In general, when you connect lun's which are in the Active File System (AFS) on a snapmirror destination or inside a (SME) snapshot of the snapmirror destination, the lun has the following VSS flags on it:
- readonly
- Hidden
- No default Drive Letter
- possibly shadow copy.
VSS framework is responsible for removing those flags only from the Active File system on the source, just after the backup.
The flags therefore remain set inside the snapshot (they are not set on destination volume AFS, but that would be inconsistent and you should not mount that).
So, if we agree you need to mount the lun inside the consistent SME snapshot of the destination, then Next you need to clear the flags manually or connect the lun inside the snapshot using SnapoDrive.
SnapDrive will do all this for you, if you chose the correct lun path inside the snapshot. It will also break the snapmirror for you, so no need to do that manually.
hope that helps,
Domenico