2012-05-31 08:35 AM
This was brought up to me and I am not sure if WFA could handle something like this, here are the two use cases given, which are basically the same:
1. A customer has an existing array with volumes on it and purchases a new array for snapmirror protection and needs to create all the mirror destinations on the new array
2. A customer has an array to be replaced and brings in a new array and needs to create all the mirror destinations on the new array
Is it possible to use an existing volume in the environment or possibly some other entity like an igroup, to be used as a template for the creation of an new volume? So basically I would want to make sure the size, vol options, snap reserve, snap sched, dedupe sched, and stuff like that match the source volume on the second array?
I am hoping this is something simple that I am totally not thinking of...
Solved! SEE THE SOLUTION
2012-06-01 03:00 AM
Yes, this is possible. While you can't use an existing volume as a WFA template, you can use a finder to find the existing volume object. Assuming you named the found volume object volFound, you can get the size from volFound.size_mb, the name from volFound.name, snapshot settings from volFound.snap_sched_options, etc.
If you'd like to do this for all volume on an array, use a loop in WFA that iterates through all volumes.
2012-06-01 07:23 AM
Well, I din't get my hands on WFA yet. So I might not be able to answer your question exactly. But a small thought. In general, the new volumes what you create inherit many their settings from the root volume settings like the guarantee, nosnap etc. So, plan accordingly by setting the options on the root volume most likely to be used on the system.
2012-08-07 06:33 AM
how can I use such a loop in wfa for all volumes in an array? I would like to use this to check if a snapmirror relationship exists for all volumes on an array. I didn't find it in the docs.
2012-08-07 08:36 AM
We're working on putting getting more documentation / training information available, but in the meantime, here is what I would recommend:
If you would like to see this in a workflow, I recently posted a c-mode workflow that will remove a vServer and all it's volumes. While not your use case, it should still prove to be a good example for how to identify all the volumes on a controller and perform various actions. You can find that workflow example HERE.
Hope this helps,