Archive Snapshot (cloning)

Question

In speaking to an EMC rep i was told i can take a snapshot and "clone" it so that it would not have to be part of a schedule that will be deleted after X days.

If any of you know how I can take a snapshot that doesn't get deleted after X days or take an existing snapshot and copy it. I should also note that i have 2 VNXe 3100 which are replicating.

The goal is i want users accessing VNXe-1 and have that data Replicated to VNXe-2. i have a snapshot schedule set for VNXe-1 (which then mirrors on VNXe-2). However VNXe-2 has 3 times the amount of storage and i have it that way so that i could archive snapshots or "clones" of NFS and CIFS shares.

Your help is much appreciated.

rajnvr1 · Answer

At the moment, VNXe does not allow creation of snapshot clones. We cannot create any snapshot clone in VNXe and cannot set the expiry date of the snapshot to infinite.

The VNXe will not allow changing any setting on the destination side, so we cannot create a schedule or takes a snapshot on the destination side.

brendm · Answer

Rohan is right - we have to be sure to differentiate between the VNX and VNXe software. Yes, they are within the same family, but they do not have all the same functionality. As the VNXe system lineup matures and we have time to quality assure features, the team is interested in exposing more file-level functionality.

brendm · Answer

Rohan, you hit the matter on the head at the nice high level, but I'm inclined to dig in to make sure the point is clear to others.

It is true to note that the VNX is the progression of the CLARiiON and Celerra line ups, but the hardware, software and architecture has progressed significantly.

More drastically, the VNXe is related to the Celerra/CLARiiON lineup like modern human beings are related to primates. The VNXe has evolutionary roots in the File and Block concepts of these systems, though I love the opportunity to show people how much has changed, from Linux underbelly to C4LX virtualization and so on. That's a much bigger conversation.

The big conclusion is that these systems are family, but they are discrete architectures with particular expectations. Be sure to read their specific documentation at http://www.emc.com/vnxesupport

rajnvr1 · Answer

Matt you are 100% correct

VNXe = Celerra + CLARiiON merged with hardware and software and SP Playing the main role.

VNX= Celerra + CLARiiON merged without hardware and software but only the Array management is merged for the ease of management

Rohan

DaveFoley · Answer

We have a similar setup to yours with 2 VNXe 3100 units. 1 source with just CIFS and the other one just as a DR replication destination. It would seem that since this thread was started, snapshots have now been enabled on the destination side (Rohan was mentioning that destination snaps couldn't be taken, but they can now).

But I tried today to increase the retention period and it still will not go beyond 31 days.

I would like to be able to take a monthly snapshot on our destination unit and keep each snap for 1 year, which is the mandated data retention policy where I work. I currently have to take backups to tape to retain them for that period.

Does anybody know if there are plans any time soon to alter the code and add the ability to change the retention period for snaps on VNXe to be more than 31 days?

Thanks,

Dave

DynaDin · Answer

As of today, I've not heard any plans to change this retention policy. You can sumit an enhancement request in http://powerlink.emc.com

DaveFoley · Answer

Sounds good!  I've submitted the request.

mpgordon · Answer

Dave,      Product management has received the enhancement request.  It will be reviewed and prioritized for a future release. Mike

VNX

Archive Snapshot (cloning)

Was this post helpful?