Unsolved
This post is more than 5 years old
16 Posts
1
1070
February 13th, 2012 10:00
Vplex virtual volume expansions
Pretty easy now to offer quick expansions of existing virtual volumes on the vplex. I didn't offer that to my vmax or dmx customers. Wondering what others are doing out there? Concatenated expansions make me nervous even with vplex in the mix if it's a true concatenation. Thoughts?
We are a couple months away from metro replication. If replication is performed at extent level and capacity add is at the virtual volume level, what steps are taken at the DR side?
jeff
No Events found!
jeffwade_96e6ca
16 Posts
0
February 13th, 2012 12:00
Nervous for performance reasons only. I default to striped for everything and avoid concatenated as often as possible. VPlex and using thin pools on the Vmax changes things a bit, so wanted to ping the community network for any feedback.
ankur.patel
2 Intern
•
286 Posts
0
February 13th, 2012 12:00
Jeff, why do concatenated expansions make you nervous? Since you are using RAID protected volumes on the backend there shouldnt be any availability issues. That being said I would say the customers I deal with are using 1:1 mapping, then expanding by migrating to another 1:1 mapped volume. This is really so they can use the backend array features like cloning/snaps/replication.
To answer your second question. Today to do a volume expansion for a distributed copy the volume needs to be converted back to a local volume, expanded, then the distributed volume recreated. Doing this while the keeping volume distributed is being looked at.
hope this helps
ankur.patel
2 Intern
•
286 Posts
1
February 13th, 2012 12:00
I would agree with your assessment of using striped for everything, probably the best way to consistent performance.