Another way to move your non-collocated data to a collocated pool is as
follows:

1) Assume you start with a pool of tapes called "OLDPOOL", which is
non-collocated.
2) Create a new tape pool called "NEWPOOL", which is collocated.
3) Send all of your new backups to "NEWPOOL" and they will be
collocated. At this point no new data is going to "OLDPOOL".
4) Update the definitions of "OLDPOOL" and specify "NEWPOOL" as the
"next storage pool" for "OLDPOOL".  When data is migrated from "OLDPOOL"
to "NEWPOOL" it will be collocated.
5) You can then control migration from "OLDPOOL" to "NEWPOOL" by
adjusting the hi and low migration thresholds. Since, It may take quite
awhile to migrate all of the data from "OLDPOOL" to "NEWPOOL" you may
want this migration to occur only between the daytime (for example). You
could issue a "upd stg oldpool hi =0 low=0" to turn it on. Issue "upd
stg oldpool hi=100 low=100" to turn it off.  Hope this helps.
Michael Yelle

> -----Original Message-----
> From: Nicholas, Murray, Haltek/AU [SMTP:MurrayNi AT HALTEK.COM DOT AU]
> Sent: Sunday, February 08, 1998 5:17 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: Collocation question...
>
> Collocation settings tell ADSM where to put data as it is written out.
>  If you want existing backup data to be affected by a change in the
> collocation parameter, you would expect that data to be physically
> moved from on storage location to another.  Since there was no frantic
> tape mount activity following the change in your settings you can be
> quite sure that your old backup data is still all jumbled together.
>
> If you really feel that you will gain some benefit from forcing old
> backup data to be collocated now, I suggest you look at the MOVE DATA
> command.  I won't guarantee that this will help though since my memory
> tells me that the syntax specifies a source tape volume and a target
> storage pool.  Collocation also specifies a relationship between nodes
> and storage pools so you will probably only achieve a bit of wear and
> tear on your drives and tapes.
>
> Murray Nicholas
> IT Systems Consultant
> Galeforce Information Services Pty Ltd
> email:  murray AT galeforce.bu.aust DOT com
>
> ----------
> From:  sbm[SMTP:sbm AT HURON DOT NET]
> Sent:  Saturday, 7 February 1998 15:53
> To:  ADSM-L AT VM.MARIST DOT EDU
> Subject:  Collocation question...
>
> I have enabled collocation on our tape pool in ADSM and things seem to
> be going well.  Here's the question - can I force ADSM to collocate
> data which has already been backed up?  Or, is this simply a setting
> which applies to future backups?  If I can force a collocation please
> let me know how.  Thanks.
>
> Steven
> <<File: ATT00007.html>>