you can obtain the steps from Symmetrix DMX Procedure Generator found at:
Home > Support > Product and Diagnostic Tools > Symmetrix Tools > Symmetrix Procedure Generator
1) create metas 2) map devices to FAs 3) mask devices to host WWNs (i am not sure if you need to mask BCV, depends if you use them for backups, reporting ..etc) 4) create temporary device group and add new STD and BCV to it. 5) perform full establish 6) once fully established, look at devices status of existing production group, if all devices are in synced state ..simply move your devices from temporary group into your production group (symld -g tempgroup moveall prodgroup -rename). If devices in prod group are split ..you need to split devices in your temporary group and then move them to production group. That way all devices are in consistent state and it will not tank your daily sync job.
Let us know if you need help with specific steps. No outage is required for any of these steps.
I want to add additional 1TB to the existing sym group ...
I have 100 STD =====100 BCV already .....
i want to add to this group....is there any outage required for doing this or it can be done online?
Also I need the steps for doing this..
i want step creating meta/map/mask for STD as well as BCV and adding to the existing symdg group... and it should be part of daily incremental sync...do we need full sync STD to BCV when we add to the DG?
can you send the steps for adding to the existing sym group? the time associated with production to BCV Sync is not a concern at this point.
I have completed the meta creation through EMC control center.
is the meta creation for BCV also same like STD?
mapping /masking for BCV same as STD? while we add to sydg ,any operation will effect production data? i need to also map and mask the BCV to another two host.
After meta creation what are the exact steps?
do we have to add to symdg after mapping and masking or before mapping and masking..
I have my sync/split script running on different host than the symmetrix management host, is there anything to take care for that..?
can you send the steps for adding to the existing sym group? the time associated with production to BCV Sync is not a concern at this point.
if you created a temporary group for new STD and BCV devices and you are ready to move them into production group after they have been fully established, the command is:
in this example you are moving STD and BCV devices from temporary group to production while renaming logical devices names at the same time. If your production group looks like this:
Standard (STD) Devices (5):
{
--------------------------------------------------------------------
Sym Cap
LdevName PdevName Dev Att. Sts (MB)
--------------------------------------------------------------------
DEV001 N/A 037E (M) RW 4313
DEV002 N/A 065C RW 8632
DEV003 N/A 065D RW 8632
DEV004 N/A 065E RW 8632
DEV005 N/A 065F RW 8632
}
BCV Devices Locally-associated (5):
{
--------------------------------------------------------------------
Sym Cap
LdevName PdevName Dev Att. Sts (MB)
--------------------------------------------------------------------
BCV001 N/A 080B (M) NR 4313
BCV002 N/A 07D0 NR 8632
BCV003 N/A 07D1 NR 8632
BCV004 N/A 0969 NR 8632
BCV005 N/A 096A NR 8632
and your temporary group looks like this:
Standard (STD) Devices (2):
{
--------------------------------------------------------------------
Sym Cap
LdevName PdevName Dev Att. Sts (MB)
--------------------------------------------------------------------
DEV001 N/A 014E RW 8632
DEV002 N/A 014F RW 8632
}
BCV Devices Locally-associated (2):
{
--------------------------------------------------------------------
Sym Cap
LdevName PdevName Dev Att. Sts (MB)
--------------------------------------------------------------------
BCV001 N/A 0239 NR 8632
BCV002 N/A 023A NR 8632
}
after you complete the move steps with "-rename" option your production group will look like this:
Standard (STD) Devices (7):
{
--------------------------------------------------------------------
Sym Cap
LdevName PdevName Dev Att. Sts (MB)
--------------------------------------------------------------------
DEV001 N/A 037E (M) RW 4313
DEV002 N/A 065C RW 8632
DEV003 N/A 065D RW 8632
DEV004 N/A 065E RW 8632
DEV005 N/A 065F RW 8632
DEV006 N/A 014E RW 8632
DEV007 N/A 014F RW 8632
BCV Devices Locally-associated (7):
{
--------------------------------------------------------------------
Sym Cap
LdevName PdevName Dev Att. Sts (MB)
--------------------------------------------------------------------
BCV001 N/A 080B (M) NR 4313
BCV002 N/A 07D0 NR 8632
BCV003 N/A 07D1 NR 8632
BCV004 N/A 0969 NR 8632
BCV005 N/A 096A NR 8632
BCV006 N/A 0239 NR 8632
BCV007 N/A 023A NR 8632
is the meta creation for BCV also same like STD?
identical, if you are creating striped STD meta ..you have to create striped BCV meta. Meta member count has to be the same too.
mapping /masking for BCV same as STD? while we add to sydg ,any operation will effect production data? i need to also map and mask the BCV to another two host.
exactly the same steps for masking STD and BCV devices. Adding new devices will not effect production. The only thing that i mentioned in my last post is before you move devices from temporary group to production .. make sure devices in temporary group are in the same TimeFinder state (either split or established) as production. This way if your script issues commands against device group it will not tank saying "device is already in specified state" or something of that nature.
After meta creation what are the exact steps?
you have to map devices to your FAs and mask them to your hosts. The steps are explained in great details in "Symmetrix DMX Procedure Generator"
do we have to add to symdg after mapping and masking or before mapping and masking..
it does not matter, your choice.
I have my sync/split script running on different host than the symmetrix management host, is there anything to take care for that..?
you will need to update these hosts with new devices. If your management host contains the group that has all devices in it, then you export this device group to a file and import it on the other hosts. To export device group on the management host you will need to run "symdg export prod_dg -f prod_dg.txt -sid 123". This steps creates a file called prod_dg.txt that contains your STD and BCV devices. You can actually open it vi or notepad and see it's content. There are some situations where it's good to know it's content and know that you modify it. Now you will need to copy this file to your other systems (ftp, rcp, ssh ..etc). If your device group names are identical between your managment host and other system, you will first need to delete the device group and then import it from the file. So on one of the other hosts you first run "symdg export prod_dg -f prod_dg_backup.txt -sid 123" to create a backup of your existing group, then you run "symdg delete prod_dg -force". This step deletes this device group. Next you run "symdg import prod_dg -f prod_dg.txt". At this point if you run symdg list -sid 123, you will see your brand new device group that should identical as the one on your management host.
then normal sync/split ( which is incremental in my case ) will take care of the Establish and split.. that looks like easy to me. but dont know any issues with that.
Then import the DG and populate to all servers which are using this device group
the new STD and BCV devices have to by fully established, so you have two choices, either create a temporary group and run "symmir -g temp_group" establish -full" or add new devices to the production group and "symmir -g prod_group establish -full DEV005 BCV ld BCV005 DEV006 BCV ld BCV006". Here i am doing a full establish on two new STD devices. If your daily timefinder scripts simply runs the establish command against your production group ..it will fail when it gets to your newly added devices unless you fully establish them prior.
if you dont prefer to import a tempdg then do a full sync using "file based"(put the entr of STD and BCV on a file) and once est/spit then go ahead with symld&symbcv steps metioned above
Is this necessary to use "-rename" option while moving to prod_gp? does this add (append) the new devices to existing group?
As i'm a child learning symmetrix please explain
"you will first need to delete the device group and then import it from the file. So on one of the other hosts you first run "symdg export prod_dg -f prod_dg_backup.txt -sid 123" to create a backup of your existing group, then you run "symdg delete prod_dg -force". This step deletes this device group. Next you run "symdg import prod_dg -f prod_dg.txt". -- deleting and importing device group we require scheduled down time? Am I right?
dynamox
11 Legend
•
20419 Posts
•
87439 Points
948
0
Posted February 20th, 2009 16:00