I'd add a 4th possibility ... RMAN backup to disk which is then (NBU 
user) backed up.  Agent not required. (I'd much rather have the NBU 
Agent, but it may be cost prohibitive).  I have a couple of Oracle 8 DBs 
backed up this way.

Also, someone (I think in this thread) mentioned you needed an Oracle 
repository to use RMAN.  Not true ... Oracle will maintain the data in 
the control files if you don't use a repository (the "nocatalog" 
parameter on the RMAN command).

RMAN is your friend.  In my limited experience, you are much more likely 
to have a restorable backup if you used RMAN than any other method 
(unless you actually test restores).  Like it or not, if you're being 
asked to protect the DB, you're the/a DBA.  RMAN may simplify the backup 
process, in addition to, as Curtis explains, the (shudder) restore process.

Finally, consider creating a test DB so you can build and test your 
backup and restore without impacting or accidentally impacting your 
production.

cheers, wayne

Jeff Lightner wrote, in part:
> In summary I was discussing 3 different things:
>
> Cold backup 
> DB down - NBU "standard" backup of the filesystem(s) or raw device(s)
> containing DB spaces.
>
> Hot backup
> DB in "hot backup mode" - NBU "standard" backup of the filesystems(s) or
> raw devices(s).
>
> RMAN backup
> DB up - RMAN feeding the backup to NBU with Oracle add on using RMAN
> repository and RMAN/NBU-ORACLE scripts.
>   
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu