Yes I fractured the Clone and added it to the Host Staorage Group. I then pulled it out of the Clone Group to see if that was the problem and it wasn't. I had the same problem with my Snaps

clone is mounted on the host other than the one with source lun ?

Yes That is correct. I have a SAN Copy replica from the Production site and I've created a clone for those so the source or the target have no host associated with them. The Clone or the Snaps from the Replica mount Read Only. I can get the Snaps to mount Read/Write if I use Replication Manager to mount the Snap.

out of curiosity ..run mountvol

then run mountvol E: /d (or whatever the drive letter is assigned to your clone, this will unmount the drive)

and then run mountvol E: \\?\Volume{9b7ae744-7695-11dc-aa45-806e6f6e6963}\ (substitute your Volume name, this will mount the drive)

I am getting the same message and cannot write to the volumes. What is confusing to me is if I run the mount in RM 5 they are fine. If I mount them in Navisphere they are read-only. I have to be missing something in this process. Do I have to manually mount using scripts or something to that effect? They will have to be mounted to different hosts for testing. The current tests are being run with SQL data but I will have file systems and our Exchange environment at the test site as well and would hate to license RM just to run a mount once in a while.

unfortunately i do not have any experience with RM, i am just curious what RM is doing to mount these volumes RW.

Yes me as well. If i mount the same volume with RM that I mount manually, it is RW.

if you have a test box, can you create a new lun on the array that contains SanCopy target luns..present it to this test box, write signature and create a partition. Then create a clone of this lun, let it's state change to synchronized, fracture it and present it to another box and see if it gets mounted, just to eliminate SanCopy from the picture.

Having a SAN Copy job from to source to target and then clone the target to present a LUN to a secondary host is as per EMC best practise so should work without any problems.

My suggestion would be to have Admsnap installed on the mount host (and also production so that you can possibly script all this in the future) and use admsnap commands to activate and present the clone LUN to the host.

For clones the command would simply be: Admsnap clone_activate
For snapshots it would be: Admsnap activate -s MySession_Name -d drive_letter:

Needless to say that both Navisphere Agent and CLI needs to be installed as well. Please also avoid using a terminal services connection or actually having terminal server installed on the mount host as it can lead to erratic behaviour¿

I posted over in RM and James Baldwin directed me to unset the VSS Hidden and Read Only attributes in diskpart. That worked like a charm!

Thanks for all the help! It is greatly appreciated.

DR

VSS Read Only and Hidden attributes in Diskpart

how did you change those parameters with diskpart ?

I used the attributes comand:

ATTRIBUTES VOLUME [SET|CLEAR] [HIDDEN READONLY NODEFAULTDRIVELETTER] [NOERR]

Diskpart>att vol clear hidden
Diskpart>att vol clear readonly

Diskpart>detail volume

Readonly: No
Hidden: No
No Default Drive Letter: Yes

good stuff ..thank you for sharing.