We're doing it. It's ugly, because ADSM doesn't really support this, but it
can be done.

You need to update the volumes to an access of 'readonly' or 'unavailable'
(if readonly, an attempt to use one that's off-site will prompt you to check
it in, unavailable will fail the attempt) and then check them out. I don't
think DRM can handle this (it couldn't in version two, and I haven't looked
since) so your D/R process is up to you.

TomK
NIBCO, Inc

> -----Original Message-----
> From: Eric Tang [SMTP:tangeric AT HK1.IBM DOT COM]
> Sent: Tuesday, September 21, 1999 7:41 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      offsite minus one version backup tape
>
> Hi All,
>
> In my environment, bascially there are 3 types of backup,
> 1. adsm filesystem backup,
> 2. archive on filesystem plus oracle archived log,
> 3. oracle database backup by connect agent
>
> For 1 & 2, I think backup storage pool will be a good solution. But for
> item 3,
> because of large databse size and number of backup retention, there
> involves a
> large number of tapes (~900 3590 tapes), backup storage pool is not
> desirable.
>
> Does anyone have an procedures to handle this kind of 'offsite minus one
> version
> backup tape'? Thanks in advance.
>
> Regards,
> Eric Tang