John, DB backups are controlled by the SET DRMDBBACKUPEXPIREDAYS value if
you use DRM.
Lacking the DRM feature you will have to use volhist info and from there
use the Q VOLHIST TYPE=DBBACKUP to look at the backup sequence sets (if u
use full and incremental DB backups) . Based on the date stamps you will
then have to track a volume to see when u can delete it and place it back
in SCRATCH status. This normally is a fixed number of days after which DB
recovery is of no use to you. In our site this is tied in with how long we
keep our stgpool volumes after ADSM has flagged it for re-use......as found
in the STGPOOL (I think that's where it is) REUSE value.

Regards

Campbell Esplin
Excalibur Business Solutions
----------
> From: John Schuch <John.Schuch AT ADVOCATEHEALTH DOT COM>
> From: John Schuch <John.Schuch AT ADVOCATEHEALTH DOT COM>
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: SENDING DATABASE BACKUPS OFFSITE
> Date: Tuesday, February 03, 1998 7:40 PM
>
>    How can offsite rotation of Database backups be
>    accomplished when you are specifying "scratch=yes" on the
>    backup db command?  The volumes are not part of a storage
>    pool.  They are only listed in the Volume History Log.
>    That is to say you cannot update a Database Volume to
>    access=offsite like you can with a volume in a storage
>    pool.  Is it possible to create a storage pool to use for
>    Database backups only?