The SRDF & Clone piece does indeed add a wrinkle to things -- you'll basically need to tear down the SRDF & Clone relationships, perform the meta expansion, then recreate the SRDF & Clone relationships with new devices that match the meta config & size of the expanded production device.  For the expansion process itself, the Symm will handle the process of copying data to the clone/bcv and back. You don't have to do anything with masking, and you don't have to present the bcv to the host. You do have to create the BCV, and it has to have the same meta config & size of the current prod device, and it has to be fully & persistently allocated. And because the BCV is fully & persistently allocated, your prod device will end up fully allocated at the end of this process -- but you can perform a zero space reclaim to thin it out again.  Here's an example of creating a fully & persistently allocated BCV meta:  -- symconfigure -sid 3905 -file preview  create dev count=1 size=109228 CYL, emulation=FBA, config=TDEV binding to pool=S1000_8R6; create dev count=5 size=109228 CYL, emulation=FBA, config=TDEV;  -- symconfigure -sid 3905 -file preview  form meta from dev 65d, config=concatenated; add dev 65e:662 to meta 65d;  -- symconfigure -sid 3905 -cmd "start allocate on tdev 65d start_cyl=0, end_cyl=last_cyl, allocate_type=persistent;" preview  -- symconfigure -sid 3905 -cmd "convert dev 65d to BCV+TDEV;" preview  And here's an example of how you'd use that BCV meta (device 65d) to expand an existing striped meta (device 39c), effectively adding two more same-sized meta members (3a0 and 3a1):  symconfigure -sid 3905 -cmd "add dev 3a0:3a1 to meta 39c, protect_data=TRUE, bcv_meta_head=65d;" preview  Just keep in mind that before you do this, you'll need to tear down the replication relationships, create the BCV to protect data, and create the new devices that you'll want added to the meta (leave them unbound). And after the process is done, you'll have to recreate the replication relationships and perform a zero space reclaim (if desired).  It's also worth noting that, as NYY mentioned, the restriping process can take a while, and there will be a config lock taken against the array while it is in progress.  Hope that helps... There's good info on this in the Solutions Enabler 7.5 Array Controls guide as well.
Subject says it all. I've got several LUNs that are going to need to be replaced by larger LUNs. I know that I can TF/Clone so long as I have the same number of meta members, but I was wondering if there was an easier method.
What's the best way to move from one striped LUN to a larger striped LUN?