IMHO you are going to do just the same but with a lot of additional hassle
(and room for mistakes).
Will you set all existing tapes to read-only or keeping them isolated in
old tapepool is nearly equivalent. The only benefit I can see is
granularity - you can slowly collocate nodes one-by-one instead of
all-at-once. But that is one of the purposes of `move nodedata` command,
thus again no difference.

Zlatko Krastev
IT Consultant






William Rosette <Bill_Rosette AT PAPAJOHNS DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
06.08.2003 17:36
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: Collocation from nocollocation


I have the following steps on how to migrate collocation instead of the
global collocation=yes on TAPEPOOL.  Would appreciate any comments,
corrections, additions, or anything constructive

Collocation Needs
i.    Build new TAPEPOOL with collocation turned on
ii.   Build new Policy Domain (preferably 2: Class1 and Class2)
iii.  Build Management classes (preferably 5: Daily, Monthly, Year7,
Year2,
and 30day)
iv.   Build Backup Copy Groups with correct policies pointing to new
tapepool
v.    Build Archive Copy Groups with correct policies pointing to new
copypool
vi.   Allocate database extra space
vii.  Add admin schedules for Migration (TSM), Reclamation, and Backup
(start_daily.sh)
viii. Copy client schedules with new Domains
ix.   Change 1 backup client to new Policy Domain.  Once starts working
start viii and keep moving backups to new Policy Domains while verifying
correct backups (check by doing restore with ?pick)

Thank You,
Bill Rosette
Data Center/IS/Papa Johns International
WWJD