It can be turned into a metavolume non-disruptively but it depends on what type of meta configuration you want. If you want a concatenated metavolume you can simply convert it into a concat meta with no host downtime. Specify the in-use device as the meta head. The member(s) that are to be added must be unbound and not have any masking records. This has been enabled in SE and Enginuity for well over a year or so. If you want a striped metavolume it has a few extra steps though. Converting a single volume into a striped volume is not possible directly without dataloss. You need to first convert the device into a concatenated meta and then you can convert that into a striped one with data protection. You will need to setup a identical concatenated meta (of type BCV) that is persistently allocated to store the current data in the background the concat to striped conversion is occurring.
Hi , I allocated few luns today to a windows host for testing purpose.and tried doing a stripe expansion. the issue we are facing is the disk which is allocated to the host is 34 GB in size. it is a tdev and the max hyper size in our vmax is 34 GB so the lun which is allocated to the host is not a meta but a hyper of 34 GB. I want to expand this Hyper . Is this possible , what are the limitations (if possible) Also , data integrity will be there or not.
Hyper expansion is possible ?