I have a customer who has successfully replicaed (via snapmirror) a volume containing a SMSQL backup. They were able to succesfully create a flexclone of the replicated volume and confirm that it's online.
They are also running snapdrive 6.0.1 on the Windows server in DR. Normally, all you have to do is go into snapdrive and connect to the filer's volume/lun. For whatever reason the flexclone volume does not show up in the list of volumes on that filer.
Is there something else that needs to be done for snapdrive to be able to see that flexclone volume? Normally, with snapdrive 6.0.X there is no longer the need to share out the volume first before snapdrive can see it - just automatic. Yte, I even went so far as to create a CIFS share for the flexclone volume and snapdrive still cannot display it.
If someone could point out what's wrong I'd appreciate it.
Are they trying to create the FlexClone from within SnapDrive itself (connecting to a SnapMirror destination will do this for you), or have they created the FlexClone outside of SnapDrive, and are now trying to connect to the cloned LUN?
The flexclone was created via filerview first. They went into filerview on the DR site and created the flexclone volume. So you have a bigger picture - The production site has SMSQL up and going. After the backup a snapmirror is kicked off to replicate the databases and logs to the DR site. We didn't want to upset the replication from happening by basing the flexclone at the DR site on the snapmirror snapshot, so a SMSQL backup was created (so the replicated data would be in an application consistent form) and a manual snapmirror performed. We based the flexclone snapshot off of that manual SMSQL backup.
Anyways, we went into filerview on the DR side and created the flexclone volume successfully. The LUN contained in this volume had no initiator maps, which was expected. At this point I'd expect to be able to go into snapdrive on the DR side and connect to the flexcloned lun - mapping the initiators as part of the process. Not sure why we can't see the flexcloned volume though.
Could you explain how we could create a flexclone from snapdrive - keeping in mind that all work is being done at the DR site? If that's possible then I'll tell them to always use snapdrive to create the flexclone, rather than using filerview or the CLI.
Simply go into SnapDrive and point to the SnapMirror destination. SnapDrive will prompt you that this is a SnapMirror destination, and provided FlexClone is licensed, it will create a clone for you and map it.
Just to confirm (sorry, just a sanity check), the LUN you have already cloned, is this definitely online? The FlexClone process may have turned it offline to prevent conflicts with LUN mappings (as it is an identical clone.
So, just to get this straight - I'm on the DR site and I can go into snapdrive here and connect to the filer here, which is the destination filer and be able to create a flexclone? How is creating the clone different from connecting to an existing lun. What I mean is there an option to 'create flexclone' or something? I know I can use snapdrive to create, connect, expand, etc., but dont see an option for create flexclone.
Can this be performed at the DR site or must it be performed from the production site?
Yup, at the DR site. The FlexClone creation is totally transparent. The idea being that a Windows administrator doesn't have to realise what a clone is, or what snapmirror is, or any of that, they just point and click.
There is no real difference between this and you doing it manually, it's just that SnapDrive takes the hassle out of it.
It should work perfectly well doing it manually also however.
Unfortunately, to connect to that lun snapdrive still needs to be able to see the volume that contains the lun - which it was not displaying. I'll try what you mentioned about snapdrive being able to create the flexclone by itself and let you know.
Hi. I've successfully created flexclones from Snapdrive. Very handy. Today, I attempted to try and create a flexclone and choose the LUN type as shared (Microsoft Cluster Services only). Unfortunately, that option is greyed out.
Is it not possible to create a shared cluster disk resource from a flexclone? I also tried to create the flexclone from filerview and connect via snapdrive, but got the same result.
My client has a MSCS in their DR site and was hoping to use flexclones of the replicated volumes for test/dev. So far no go in creating a flexclone LUN cluster (shared) disk resource.
Are you cloning from a cluster disk to a cluster disk, or are you trying to clone a standalone disk into a cluster? The disk signatures will be brought across, and this will identify whether it's a standalone or cluster disk. I've never had to try changing it to be honest, so I'm not sure I'm afraid!