The way we do our Oracle backups is a bit different.  Once a month (during
our special month end processing) we shut down Oracle and do a cold backup
of the Oracle DB files.  The rest of the time we simply back up the Redo Log
Archives.  This can make for a long restore depending on how long it was
since the cold backup but I've only had to do it twice in 9 years (and one
of those times was entirely my fault).  You could modify that and do a cold
backup once a week which would reduce the potential number of redo log
archives you need to restore.

Other parts of our Oracle backup 'system' include directives (in .nsr files)
that specify skipping the Oracle database (*.dbf) files, a couple of scripts
to rename the .nsr files during the cold backup so those (.dbf) files are
backed up (and then to rename the directive files back to .nsr).  There is
also a script that monitors the space available on the file system where the
redo log archives are written and triggers a backup and deletion of those
files when the fs gets too full.

If it makes any difference we are running all of this on Solaris but the
Networker Server is on W2K.

David Werth
Garmin AT, Inc
(formerly: UPS Aviation Technologies)
(formerly: II Morrow)
Salem, Oregon
dave.werth AT garmin DOT com

-----Original Message-----
From: Matthew Huff [mailto:mhuff AT OX DOT COM]
Sent: Thursday, January 15, 2004 8:40 AM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] I just don't seem to get it... Are there other do c
resources?

I agree with what Terry is saying. A file level backup of a running
Oracle database is worthless without special consideration.

However, I would argue there are three levels of backups you can do with
Oracle and Legato.

1) Cold. Database has to be shutdown. You can use Legato's pre and post
command to run a script to shutdown/startup database. This is actually
the easiest to restore and the least complicated. However the database
has to be completely shut down during backups and you always run the
risk of the database not restarting for the next day.

2) Hot. You can use a script to put Oracle's tablespaces in "hot backup"
mode while backup is running. File level backup is then possible. This
is fairly complicated and error prown. However, you can backup the
database without shutting it down or purchasing other licenses.

3) Rman. You can use Oracle's RMAN with Legato's module for Oracle to do
backups without shutting the database down, nor putting the database in
"hot backup" mode. The database wont' see near as a performance impact
as the normal Hot backup causes. However you need to buy Legato's
license. Generally around $5k per Oracle server.


--
Matthew Huff           | One Manhattanville Rd
Director of Operations | Purchase, NY 10577
OTA LLC                | Phone: 914-460-4039
mailto:mhuff AT ox DOT com    | Fax:   914-460-4139




            -------------------------
This e-mail and any attachments may contain confidential material for the sole 
use of the intended recipient.  If you are not the intended recipient, please 
be aware that any disclosure, copying, distribution or use of this e-mail or 
any attachment is prohibited.  If you have received this e-mail in error, 
please contact the sender and delete all copies.
Thank you for your cooperation

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=