UNSOLVED
Composite Groups best practices
We're researching using composite groups (CGs) instead of device groups (DGs) because we're running out of storage on some of our DMX arrays and need to add storage fom other arrays to some of our Datbases that we create CLONEs of.
Currently we create CLONEs (via DGs) for backup and QA testing purposes primarily. We also RESTORE from these CLONEs when needed.
My request/question is very general:
- What are best practices?
- What are the "gotchas"
- Any tips on how to migrate from DG to CG CLONEs? We assume we'll have to TERMINATE the DGs and then reCREATE the CGs.
Thanks in advance!
Currently we create CLONEs (via DGs) for backup and QA testing purposes primarily. We also RESTORE from these CLONEs when needed.
My request/question is very general:
- What are best practices?
- What are the "gotchas"
- Any tips on how to migrate from DG to CG CLONEs? We assume we'll have to TERMINATE the DGs and then reCREATE the CGs.
Thanks in advance!
rawstorage
4 Apprentice
•
423 Posts
229
0
Posted January 14th, 2009 02:00
There should be no need to terminate the clones beforehand.. They will still work.
xe2sdc
6 Operator
•
2831 Posts
229
0
Posted January 12th, 2009 08:00
Best practices or gotchas ?? I guess other may help you .. I have no suggestions here...
But I can help you in switching from DG's to CG's smoothly ..
Have a look at the command
symdg [various other options] dg2cg
I'm not 100% sure but I guess you don't need to terminate clones since the relation is inside the storage (and not in the device gruop).