Oracle export (or Data Pump in newer versions of Oracle) may give you 
the protection you need.

    * Have your DBA evaluate the export(s) done and test restores. 
      Tests may include loss of
          o an Oracle row of data
          o an Oracle table
          o an Oracle tablespace
          o an Oracle schema
          o an Oracle full database
          o an Oracle home and database
          o (Note that each bullet above is generally a superset of
            what's above it, though it's not uncommon for a schema to
            use more than one tablespace (and vice versa), for example.)
    * Make sure the exported data is all there when you backup the file
      system where the dump(s) reside.
    * Make sure there are backups for "stuff" not in the export(s).
          o Even though a schema might store all data in one tablespace,
            backing up the tablespace does not backup everything in the
            schema
          o Oracle control file(s)
          o init and/or spfile(s)
          o oratab, orainst, oraInventory, and ORACLE_HOME(s)
    * Consider/suggest that your DBA add "rman" backups and you capture
      those backups with either the Oracle agent, or from disk as you
      are now doing.  In my limited experience, if rman will restore it,
      the Oracle DB will start and run.
    * Once doing "rman" backups, have your DBA consider using the rman
      catalog feature.  W/o the catalog, rman keeps backup information
      in its control files.  Using the catalog feature gives your DBA
      additional flexibility. 


We're mostly a Linux and Solaris shop, with a smattering of Windows.  I 
use "export" on a few DB and the Oracle Agent with rman on another.  I'm 
considering moving my Oracle agent backups to be independent of 
NetBackup (rman backing up to NAS).  This is more of a management 
challenge (I don't see failures on my NetBackup console/reports), but 
may be a reasonable way to cut costs for us.

Cheers, Wayne

Todd Jackxon wrote, in part,  on 2009-04-22 8:55 AM:  
> Is there anyone out there running Oracle on a Windows box?
> If so can you explain how you are running your script on the client
> side for Backups?
>  
> All of our systems are Unix or Linux and the 1 Window system we have 
> is backing up by using
> some type of Oracle export scheduled task to another system and 
> backing it up
> through File System. This is not the way to go but we don't have any 
> example running
> this properly from Windows client. Any suggestions are appreciated.
>  
> Client is Windows 2003 Standard, SP2 - NBU 6.5.3.1
>  
> Master server is Windows NBU 6.5.3.1
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu