There are they types of Oracle backups:
1) Cold
You shut down the database and all active processes and back the
datafiles up
2) Warm
You use a script to set the tablespaces into backup mode and can
access the datafiles in a consistent manner. This impacts performance
during the backup, but doesn't cause the database to go offline. Check
out some scripts on http://www.backupcentral.com. You will need extra
diskspace to hold the copies of the datafiles, but you can then back
them up using regular legato clients
3) Hot (Oracle RMAN)
Allows the native Oracle tool (RMAN) to use legato to manage the tape
library. Much more complicated, but provides the best and most supported
backups. If you have ever dealt with Oracle support you know how
difficult it is if you are caught in an unsupported solution and trying
to get them to help you with it.
----
Matthew Huff | One Manhattanville Rd
Dir of Operations | Purchase, NY 10577
OTA LLC | Phone: 914-460-4039
www.otaotr.com | Fax: 914-460-4139
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Werth, Dave
Sent: Wednesday, October 18, 2006 8:37 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Is the NetWorker Oracle Module necessary?
Bhaskar,
That's essentially what we do here. But you can't rebuild with the
archive
log files unless you have a good (uncorrupted) database to start from.
So what we do is each month after our month end processing we shut down
oracle and do "cold" backups of the database files (and control files as
well). The rest of the month we just back up the archive log files.
They
do get backed up by the regular incremental/full cycle of backups but
because of limited disk space I have a cron job that periodically (every
20
minutes) checks the used space on the file system and when it reaches a
certain percentage it triggers a special Networker session that backs up
the
archive log files then deletes them. Right now this generally happens
about
once a week and backs up about 1250 archive log files. Also, I don't
bother
using a special pool for these backups. They are only for disaster
recovery
and our tape rotation is about a 3 month cycle which is plenty of
leeway.
This method has worked well for us when I've needed to restore Oracle
but
it's been about 6 years since the last time I had to restore the DB.
Of course if you have an Oracle DB that you can't ever shut down for
long
enough to do a cold backup then you'll have to use RMAN to do "hot"
backups
for your baseline backups. The longer you go between establishing the
baseline backups the more archive log files you'll need for a complete
restore. Restoring this way can be a fairly time consuming process
depending on how many archive log files you need. RMAN backups may give
you
a quicker recover time since it will be a one step restore, you won't
need
to restore the archive log files.
We are running Oracle 8i on Solaris 7 with Networker 7.2.1 on W2K. If
you
want to see the cron job and Networker backup script I'm using I'd be
happy
to send them to you.
Dave
David Werth
Garmin AT, Inc
Salem, Oregon
dave.werth AT garmin DOT com
-----Original Message-----
From: Bhaskar Mylavarapu [mailto:Bhaskar.Mylavarapu AT NOAA DOT GOV]
Sent: Wednesday, October 18, 2006 4:13 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] Is the NetWorker Oracle Module necessary?
What are the advantages of using the Legato NetWorker module for Oracle
versus just using the built-in archive log feature to back up the system
on-line and then use NetWorker client to backup the data from that?
Example: Suppose on the Oracle server, I have the basic NetWorker client
software installed, and I create a cron job that backs up the Oracle
archive log files to some storage location (say, disk) using the
built-in archive log feature, and then when the copying is done it fires
off a NetWorker save process to back up that data to tape. The save
process would specify a particular pool dedicated for these Oracle
files. Since a live database does not need to be shut down for this
purpose this seems to be a completely viable option. After all, the save
process would not attempt to back up the data files that comprise the
live database, only the ones that were written to the storage area by
the cron job - an area that wouldn't be subject to changes by users. In
fact, this seems to be an advantage over the module method since you
could then use nwrecover or saveset recover to recover the desired
files and then use Oracle recovery commands from there. Of course, when
recovering data, the database might have to be shut down, depending on
the situation, but likewise if using the module, right? In fact, if
using the module you still have to use RMAN to recover it anyway; you're
not going to use nwrecover or saveset recover.
OK, what then is the NetWorker Oracle module really giving you that the
above "example" method wouldn't? Seems like just extra cost for
maintenance and more configuration for the same results?
Would appreciate any advice. We're all for using the module, but fail to
see why we need to or what it's perks are. Inquiring minds want to know.
Thanks.
Bhaskar
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type
"signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu
if
you have any problems
wit this list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
-------------------------
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
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu
if you have any problems
wit this list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu
if you have any problems
wit this list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
