Will, a collegue of mine was able to migrate the extents of the two legs but the expandable space of the virtual volume did not change. So it seems the best way is to expand the backend lun. I have brought this up to the product management group
I guess I was looking at a way to do this without going through the meta expansion on the VMAX. That's been one of the nice things with the VPLEX and non-distributed volumes, we can do a local mobility rather than the trouble of a meta expansion. I should have stated this in my question.
So, my real question is, other than "physical" device expansion at the VMAX, is there a good way to expand a distributed volume?
Will have you checked out the admin guide? theres a whole section on expanding a volume. Assuming you are doing 1:1 encapsulation you can expand the array volume then have vplex expand the virtual volume
Will the only way ive seen this done is via backend expansion. Im going to have to try to see if one can migrate the extents of the two legs to larger volumes then expand the virtual volume
ankur.patel
2 Intern
•
286 Posts
3069
0
Posted January 2nd, 2015 07:00
Will, a collegue of mine was able to migrate the extents of the two legs but the expandable space of the virtual volume did not change. So it seems the best way is to expand the backend lun. I have brought this up to the product management group