#when do "volume move" or snapmirror, what is going to happen to associated clones?
1 messages · Page 1 of 1 (latest)
re: snapmirror - you'd have to reclone at the second site.
you can off the DP volume.
I am slow...But, it sounds no matter which one of following 4 ways I use, splitting will have to happen, and result in increasing the size to double, Right?
My goal is to move all volumes and all clones off the aggr to a new aggr. The old one will be deleted. There are a number of such volumes. Clones are in use by different QA/DEV/TEST, so, they have to be kept and transparent during the move.
- Move the parent volume. A temporary volume will be created to host the clones.
In this case, what will happen to the temp volume, what do I need to do to keep clones and still associate them with the parent after it resides on a new aggr?
- Split the clone from the parent, then move the parent to the destination aggregate. This will maintain the snapshots and the space efficiencies within the clone and the parent volumes.
After splitting, it will result in double size, right?
- Offline and delete the clones, then move the parent volume.
That is not the option, because I need to keep clones.
- Perform a 'volume move' on the volume clone. This will split the clone and the snapshots within will be deleted from the clone and space efficiencies will not be maintained.
Only move clone? what if I wanted also move volume? not mention that I also need to keep snapshots within