What's the best way to move from one striped LUN to a larger striped LUN?
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.
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 -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.
Assuming you're running Solutions Enabler 7.3 (or later) and Enginuity 5875.198 (or later), you can nondisruptively expand a striped meta, adding additional meta members, as long as you use a BCV (clone) to protect the data during the restriping process. In a nutshell, the system will copy all data to the BCV (clone), add the additional meta members to the prod device, and then copy everything back to the (now larger) prod device. Then of course you have to do some work at the OS/LVM/filesystem layer to recognize the additional space.
The BCV should be a thick or fully & persistently allocated thin device with a meta configuration that matches the source device (e.g. if the source dev is a 4-way striped meta, the bcv should be a 4-way striped meta, and the member sizes should be the same).
except TF/Clone, you can expand those metas to largers metas.
Of course it depends what kind of Storage do you have.
DMX or VMAX?
And on VMAX the Thin Pool how many TDATs devices have?
One question?
Do you want to expand them from the Storage perspective or those metas are already attached to the hosts and you want to do the expansion on the hosts?
Then you can do it via Host Mirror Copy or you can use PPME for Windows or Linux.
I've no experience creating BCV, but all of our disks are allocated to thin pools. I don't know how to copy between the BCV/ThinDev.
The OS/LVM level is pretty straightforward, but it is the VMAX side that I have a problem with. Would I need to disconnect the prod device and connect the BCV in its place?
Sorry for the scrub questions, I just don't have the experience.
the expansion method that i mentioned nad Sean described it more analytical and accurate it is online procedure and non-disruptive.
But i mentioned what kind of Symmetrix do you have, because it is going to take some time to do the expansion.
Let's if you have to expand a meta from 1TB to 2TB it is going to take time.....
So since you have VMAX and 5876 code, the Thin Pool how many TDATs have?
I performed an expansion i don't rememeber exactly what was the meta size before and after, but i had a Thin Pool with 2048 TDATs and the expansion took almost 2 hours.
Now regarding SRDF and probably Sean will confirm that you have to split the SRDF, to delete the pair for the specific device(s) and then to creata a new one at the DR Site.
That's why i told you if you can do the expansion via the Host Mirror Copy (Veritas)
One syntax change I would suggest for the commands is to use the prepare option instead of the preview option. The preview option just validate the synatx of the symconfigure command is correct while the prepare option will validate the command syntaxt and confirm that the proposed change is valid on the array.
seancummins
2 Intern
•
226 Posts
1895
1
Posted June 5th, 2013 06:00
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.