Path: utzoo!news-server.csri.toronto.edu!rutgers!ub.d.umn.edu!cs.umn.edu!uc!shamash!jeff
From: jeff@u02.svl.cdc.com (Jeff Needham)
Newsgroups: comp.databases
Subject: Re: ORACLE: Backup suggestions wanted
Message-ID: <31398@shamash.cdc.com>
Date: 14 Mar 91 20:21:16 GMT
References: <1991Mar12.134145.15364@maytag.waterloo.edu> <559@genco.bungi.com>
Sender: usenet@shamash.cdc.com
Distribution: na
Lines: 28

rad@genco.bungi.com (Bob Daniel) writes:

>In article <1991Mar12.134145.15364@maytag.waterloo.edu> psalvini@maytag.waterloo.edu (Paul Salvini) writes:
>>We at Wilfird Laurier are looking for suggestions on how to backup
>>our ORACLE databases efficiently and with as little interruptions as
>>possible. 
>>
>>So... How do you do it? 
>>  - we have done cpio and hdumps and would like suggestions to other
>>alternatives or scripts that you might be using.

>If the database is shutdown, the backup of $ORACLE_HOME directory is sufficient.

If you are even lazier and don't feel like backing all the library directories
and binaries, just back up ?/dbs/*.dbf.   Typically, tablespaces and log files
follow the convention that they have a .dbf suffix, so this would ensure
you get all the database files.  Not everyone uses this convention, and not
everyone keeps their tablespaces in ?/dbs.  A full/incremental dump script
running over $ORACLE_HOME, as above, would mean you only dump the product
directories once a week.  Sites also archieve their offline logs through
NFS to protect the production instance.

jeff
--
Waiting for the Oracle port to the Oberheim OB-Xa
| Jeffrey Needham
| Yet Another Oracle Performance Group
| Control Data - Santa Clara, CA - INTERNET jeff@hawk.svl.cdc.com