I am of the opinion that the way you are currently doing it is the best
method.  The reasons are simple:

It introduces less complexity to both backups and restores.

Both are done faster if to-from disk rather than tape.

Tape can run 24/7. The large libraries are designed for that.

What we are migrating to is a dbexports filesystem that lives on a
NetApp.  Each instance gets exported to this filesystem and the
filesystem gets backed up to tape once a week.  The filer resides in a
different building (as does the library) so DR is accomplished.  With
NetApp we take snapshots every night each week so we also have 5 copies
online in case of corruption.  You could do the same with standard ufs,
just add a move command to the end of the dba's export script.

My $.02

~JK



> "Abercrombie, Sherry" wrote:
> 
> Help!!  I need hard evidence to show to DBA's that the Oracle Agent
> for Backup Exec 8.6 will not harm their precious little databases.
> 
> Right now they do Hot Backups nightly to another location on the
> network and once that is completed I can run my backups to tape which
> means that I have backups running virtually 24 hours a day, their
> database backups and then my other backups that run nightly.
> 
> If you are successfully using the Oracle Agent for Backup Exec 8.6
> please let me know how it goes in your organization, what the
> advantages, disadvantages are, how long it takes to run & how much
> (GB's) data is backed up.  Any and all input is greatly appreciated!
> 
> TIA,
> 
> Sherry Abercrombie
> Information Technology
> Data Center Administration Team
> 

-- 
=====================
Jeff Kennedy
Unix Administrator
AMCC
jlkennedy AT amcc DOT com