It depends.  Do you have more than one copypool that you rotate between?  Do
you want to take the chance that while your copypool is on site there's a
disaster and your offsite tapes are destroyed?

We previously had 3 copypools that we rotated between.  Every day, one set
was onsite to be updated with the backup stgpool command and to be cleaned
up by reclamation.  The other 2 sets were offsite.  We did this because it
fit in nicely with our procedures for offsite tapes for other platforms.

Then, our tape usage increased and we got a 3494.  So, we changed to one
copypool.  Everyday we make a list of tapes that were added to the copypool
and need to be taken offsite.  Once a week we make a list of tapes that are
now empty and need to be returned.  We also run reclamation once a week.
With the tapes offsite, it uses the local stgpools as input and creates new
copypool tapes.

This works best for us now with our library and volume of tapes.  Multiple
copypools worked fine while we were smaller.  So, it mostly depends on your
comfort level with your copypool not being offsite all the time and how your
ADSM is configured.

If you have any more questions, let me know.

Tina Hilton

> -----Original Message-----
> From: Ann Foster [SMTP:afoster AT SEAHAWK.NSCC.MASS DOT EDU]
> Sent: Tuesday, January 05, 1999 9:07 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Reclamation of offsite group.
>
> Hello,
>         From my understanding of reclamation documentation, we are
> starting to set
> reclamation for our offsite copypool as follows: When we offsite a
> copypool, we set reclamation on that copypool to 100% to prevent
> reclamation. Then, when we return the copypool onsite we set reclamation
> back to 50%. Can any one verify if this procedure is correct, or if not,
> why a better solution should be used?
>
> Thanks for any input,
> Ann Foster
> afoster AT nscc.mass DOT edu
>
> ADSM Server 3.1.2
> AIX 4.1.5
> (We are currently not using Disaster Recovery Manager.)