Solved!
Go to SolutionC
ChristianSchmid
79 Posts
0
2849
November 17th, 2008 12:00
Symconfigure, Preview, Prepare, Commit... why run them all?
When I'm playing with new symconfigure commands I use preview to see if I've got the syntax right but that is about it. Once I'm familiar with a set of commands I normally just create my file and run it through with the commit argument.
When I get information on commands through Google or other web resources I often find people spelling out running the files through all three steps. What is the advantage of preview / preparing right before committing? problems with my commands still show up during the commit if I skip straight to that step.
Thanks,
Christian
When I get information on commands through Google or other web resources I often find people spelling out running the files through all three steps. What is the advantage of preview / preparing right before committing? problems with my commands still show up during the commit if I skip straight to that step.
Thanks,
Christian
1186
0
Posted November 17th, 2008 14:00
i see it as a sanity check before you run the commit command. Forces me to think twice what i am about to do.
I know some shops do not allow provisioning during the day or only allow provisioning during specific time frames. So it's a nice way to verify your symconfigure file before hand, so you don't have to rush and fix your symconfigure file during that short window that you have to complete your symmetrix work.1192
0
Posted November 18th, 2008 02:00
I love what Dynamox said .. and I can't tell you what I really think since I'd be fired1192
0
Posted November 18th, 2008 08:00
Stefano/dynamox,
is there any way to know the size of meta "symconfigure" going to make before commiting? I mean by preview or prepare?1192
0
Posted November 18th, 2008 09:00
i am not sure what you mean by size ..you are manually selecting meta members right ?1192
0
Posted November 18th, 2008 10:00
you are manually selecting meta members right ?
Yes.
But when you make big metas like 500Gb from 13.x hypers you have to put around 37 hypers together to reach there. Worst thing, if those hypers are not in the sequenceand you end up doing something like this
form meta from dev ED0 ,config=striped,stripe_size=2 cyl;
add dev F0D:F20 to meta ED0;
add dev F5D to meta ED0;
add dev F83 to meta ED0;
add dev F2A to meta ED0;
add dev F2C:F2E to meta ED0;
add dev F30:F33 to meta ED0;
after running commit successfully you realize the meta size is 490Gb instead of 500 Gb.
Thats why I ask you that Qs.
I think, there should be a way to know the size of meta before actually commting it1192
0
Posted November 18th, 2008 10:00
Amol you choose metavolume size
As Dynamox said, you choose member size and number of members. You can easily find how big is your metavolume with "calc.exe" (or bc if you prefer unix OSes)1192
0
Posted November 18th, 2008 11:00
yeah ..this is not Clariion where you can specify exact number of gigabytes and it will create a LUN for ya.. have you played around with "count=" option. Let Symmetrix select the best meta members for you ..plus don't have to create these lengthy config files.
1192
0
Posted November 20th, 2008 05:00
What's next? I'd do this:
dissolve meta dev ED0;
form meta from dev ED0, config=striped, strip_size=2 cyl, count=37;807
0
Posted November 20th, 2008 06:00
It does make sense to have prepare tehre to get things ready to run them later. For my case where I just do everything during the day, I'm not going to hurt anything by just jumping to commit correct?
Well... not that I'm not going to screw something up with the commands, but not anything that symm wouldn't let through preview/prepare anyways.
dynamox
11 Legend
•
20419 Posts
•
87439 Points
1305
0
Posted November 20th, 2008 06:00