Steve,
There is no such thing as a "retension period" for Copy pool tapes - tapes
only expire when the data on them expires.

The backup versions of data on a copy pool tape will have a mixture of life
spans, based on the management class requirements for the original data
files.  Some backup versions may get expired  based on the number of
versions in the management class, some backup versions may get expired based
on the number of days specified in the management class.  Only data base
backup tapes have a life span just based on days.

Tapes can go into VAULTRETRIEVE status only when all the data on the tape
has expired, or when a RECLAIM is done on them, which creates a new copy
onsite that gets moved to the vault.

Are you thinking of the "reusedelay" parm set for the storage pool?
Or could your RECLAIMS be combining data and causing tapes to return from
the vault?


===============================================================
Wanda Prather
Johns Hopkins Applied Physics Lab
443-778-8769
wanda_prather AT jhuapl DOT edu

"Intelligence has much less practical application than you'd think."
              - Scott Adams/Dilbert
===============================================================

> ----------
> From:         Steven McNicholas[SMTP:stevem AT za.ibm DOT com]
> Sent:         Wednesday, June 24, 1998 5:01 AM
> To:   ADSM-L AT vm.marist DOT edu
> Subject:      offsite storage retension
>
> Hi,
>
> If I have set my retension periods to 30 days for offsite copypool tapes,
> and I
> send a tape offsite everyday should I not have 30 tapes that are offsite
> at
> anytime?
>
> What I am finding is that some tapes are staying offsite for 30 days while
> other tapes are going into vault retrieve status after 7 days.I only have
> 1
> copypool that is set to 30 so I do not understand why this is happening.
>
> Can anybody shed some light on this?
>
> Regards,
> Steven McNicholas
> Unix system administrator
>