This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C1F75E.221D5A20
Content-Type: text/plain;
charset="iso-8859-1"
There's a couple of options with Oracle:
1. Use RMAN - Oracle's internal backup tool. This takes another license
($$) from Veritas and Netbackup will basically provide little more then
media services. It's nice if you want the DBA's fully managing the backups.
It also allows incremental backups of Oracle files - the only option to
permit this.
2. Cold Backups - Shut down oracle and send the files just using a regular
file backup. You can do this with a pre-schedule job. See the
bpstart_notify and bpend_notify descriptions in the manual. In short, you
can setup a class for the cold backup, then put the Oracle shutdown in
bpstart_notify.<classname> and the oracle restart in
bpend_notify.<classname>. Note, you usually have to increase the wait times
in the master server to allow enough time to get the DB down and up. See
the bp.conf entries fo BPSTART_TIMEOUT and BPEND_TIMEOUT. The downside is
the DB is out for the duration of the backup.
3. Rolling Hot backups - this is our internal term for this method. The
technique here is using the user-backup feature of NB. (Note the DB has to
be in log mode to successfully put a tablespace in hot-backup mode.
a. Query the database for all tablespace names
b. For each tablespace, in sequence
1. query oracle for datafiles related to the tablespace (place in a
file)
2. place tablespace in hot-backup mode
3. use bpbackup to send the list of datafiles to netbackup
4. remove tablespace from hot-backup mode
5. loop for next tablespace.
c. Alter control file to trace and send that file via bpbackup, too.
d. Roll the redo logs - wait for completion.
e. Send relavent archived redo log files, this is the set that starts from
just before the first tablespace is put into HB mode up to and
including
the last one that results from rolling the redo logs.
This makes a whole bunch of NB images, one per tablespace, that represents a
single backup of the entire database. To track these as a set, we tie them
together with a keyword based on backup date & instance name.
Restoring is a pain, compared to a cold backup, because there's a lot of
redo logs to apply to get to a time-consistent image but it does work and
the DB stays up all the time.
4. Yet another method is to do something expensive with split mirrors or
BCV's but that's too big to detail here.
If anyone has another method, let's hear about it.
HTH - Mark
-----Original Message-----
From: Mauro Palmiero [mailto:mpalmiero AT intin DOT it]
Sent: Thursday, May 09, 2002 6:45 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] pre-command and post-command
Hi,
I have a client with db oracle, I need to backup the db when It's stop, how
can do It?
Thank you.
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
------_=_NextPart_001_01C1F75E.221D5A20
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>RE: [Veritas-bu] pre-command and post-command</TITLE>
</HEAD>
<BODY>
<BR>
<P><FONT SIZE=3D2>There's a couple of options with Oracle:</FONT>
</P>
<P><FONT SIZE=3D2>1. Use RMAN - Oracle's internal backup tool. =
This takes another license ($$) from Veritas and Netbackup will =
basically provide little more then media services. It's nice if =
you want the DBA's fully managing the backups. It also allows =
incremental backups of Oracle files - the only option to permit =
this.</FONT></P>
<P><FONT SIZE=3D2>2. Cold Backups - Shut down oracle and send the files =
just using a regular file backup. You can do this with a =
pre-schedule job. See the bpstart_notify and bpend_notify =
descriptions in the manual. In short, you can setup a class for =
the cold backup, then put the Oracle shutdown in =
bpstart_notify.<classname> and the oracle restart in =
bpend_notify.<classname>. Note, you usually have to =
increase the wait times in the master server to allow enough time to =
get the DB down and up. See the bp.conf entries fo =
BPSTART_TIMEOUT and BPEND_TIMEOUT. The downside is the DB is out =
for the duration of the backup.</FONT></P>
<P><FONT SIZE=3D2>3. Rolling Hot backups - this is our internal term =
for this method. The technique here is using the user-backup =
feature of NB. (Note the DB has to be in log mode to successfully =
put a tablespace in hot-backup mode.</FONT></P>
<P><FONT SIZE=3D2> a. Query the database for all tablespace names =
</FONT>
<BR><FONT SIZE=3D2> b. For each tablespace, in sequence</FONT>
<BR><FONT SIZE=3D2> 1. query oracle for =
datafiles related to the tablespace (place in a file)</FONT>
<BR><FONT SIZE=3D2> 2. place tablespace in =
hot-backup mode</FONT>
<BR><FONT SIZE=3D2> 3. use bpbackup to send the =
list of datafiles to netbackup</FONT>
<BR><FONT SIZE=3D2> 4. remove tablespace from =
hot-backup mode</FONT>
<BR><FONT SIZE=3D2> 5. loop for next =
tablespace.</FONT>
<BR><FONT SIZE=3D2> c. Alter control file to trace and send that =
file via bpbackup, too.</FONT>
<BR><FONT SIZE=3D2> d. Roll the redo logs - wait for =
completion.</FONT>
<BR><FONT SIZE=3D2> e. Send relavent archived redo log files, =
this is the set that starts from </FONT>
<BR><FONT SIZE=3D2> just before the first =
tablespace is put into HB mode up to and including </FONT>
<BR><FONT SIZE=3D2> the last one that results =
from rolling the redo logs.</FONT>
</P>
<P><FONT SIZE=3D2>This makes a whole bunch of NB images, one per =
tablespace, that represents a single backup of the entire =
database. To track these as a set, we tie them together with a =
keyword based on backup date & instance name.</FONT></P>
<P><FONT SIZE=3D2>Restoring is a pain, compared to a cold backup, =
because there's a lot of redo logs to apply to get to a time-consistent =
image but it does work and the DB stays up all the time.</FONT></P>
<P><FONT SIZE=3D2>4. Yet another method is to do something expensive =
with split mirrors or BCV's but that's too big to detail here.</FONT>
</P>
<P><FONT SIZE=3D2>If anyone has another method, let's hear about =
it.</FONT>
</P>
<P><FONT SIZE=3D2>HTH - Mark</FONT>
</P>
<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Mauro Palmiero [<A =
HREF=3D"mailto:mpalmiero AT intin DOT it">mailto:mpalmiero AT intin DOT
it</A>]</FONT>=
<BR><FONT SIZE=3D2>Sent: Thursday, May 09, 2002 6:45 AM</FONT>
<BR><FONT SIZE=3D2>To: veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2>Subject: [Veritas-bu] pre-command and =
post-command</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>Hi,</FONT>
</P>
<P><FONT SIZE=3D2>I have a client with db oracle, I need to backup the =
db when It's stop, how</FONT>
<BR><FONT SIZE=3D2>can do It?</FONT>
</P>
<P><FONT SIZE=3D2>Thank you.</FONT>
</P>
<P><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Veritas-bu maillist - =
Veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu"; =
TARGET=3D"_blank">http://mailman.eng.auburn.edu/mailman/listinfo/veritas=
-bu</A></FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01C1F75E.221D5A20--
|
