Set up two management classes, one for normal use and one for the copy to go
off site. Use two different copy groups to point to the two different
management classes. And then set up two different init<SID>.utl files (I'd
use initPRD.utl and initPRD.off.utl, for my PRD instance, but that's just me
:-).

When you run brbackup for the off-site copy, include '-r <path
to>/initPRD.off.utl' on the command line.

My off-line script uses this to invoke brbackup:
# export BR_TRACE parm added for debugging faild shutdown 2-1-2002 trk
/usr/bin/su - ora$LOWSID -c "export BR_TRACE=15; brbackup -c -m all -r
/oracle/$SID/backint/initPRD.utl.sun -t offline_force"

And my online backups use this:
/usr/bin/su - ora$LOWSID -c brbackup -c -m all -r
/oracle/$SID/backint/initPRD.utl -t online

The script is run from the root crontab and SID is passed as a parameter.

Tom Kauffman
NIBCO, Inc


> -----Original Message-----
> From: Tait, Joel [mailto:Joel.Tait AT CCRA-ADRC.GC DOT CA]
> Sent: Friday, March 22, 2002 2:48 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: TDP R/3 Versioning and Off-site Vaulting
>
>
> Hi
>
> Does anyone have any idea's of how to use copy pools to take
> only 1 SAP DB
> Backup version off-site every week?
> Reason: Primary Pool will hold 4 - 4TB versions of a SAP DB Backup.
>
> Thanks
>
> Joel E. Tait
>
>