Veritas-bu

[Veritas-bu] pre-command and post-command

2002-05-09 10:22:13
Subject: [Veritas-bu] pre-command and post-command
From: Steve.White AT PacifiCorp DOT com (White, Steve)
Date: Thu, 9 May 2002 07:22:13 -0700
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_01C1F764.E9B2E450
Content-Type: text/plain;
 charset=iso-8859-1
Content-Transfer-Encoding: 7bit

In oracle terms that's an export and yes, you can perform a full database
export in Oracle.  Many times it's quicker to restore from an export.  It's
also a good way to go if you have multiple schemas in the database and want
to only restore one of them.

-----Original Message-----
From: Jon Walton [mailto:jonw AT n2h2 DOT com]
Sent: Thursday, May 09, 2002 6:57 AM
To: Donaldson, Mark
Cc: 'Mauro Palmiero'; veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] pre-command and post-command


Does Oracle have a built-in 'dump' command that performs a database dump
to a file or series of files?    This is how we backup our Sybase ASE
servers.   We dump to a filer, then backup that filer to tape after the
database dump has finished.

Since the database dumps stay on the filer for a few days, more often than
not, the DBA can perform restores without any interaction with the
backup/restore system.

Of course this method gets tougher and more expensive with very large
databases.

-Jon


On Thu, 9 May 2002, Donaldson, Mark wrote:

> 
> 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
> 

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

------------------------------------------------------------------------------


This email is confidential and may be legally privileged.

It is intended solely for the addressee. Access to this email by anyone else, 
unless expressly approved by the sender or an authorized addressee, is 
unauthorized.

If you are not the intended recipient, any disclosure, copying, distribution or 
any action omitted or taken in reliance on it, is prohibited and may be 
unlawful. If you believe that you have received this email in error, please 
contact the sender, delete this e-mail and destroy all copies.


==============================================================================

------_=_NextPart_001_01C1F764.E9B2E450
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.2654.45">
<TITLE>RE: [Veritas-bu] pre-command and post-command</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>In oracle terms that's an export and yes, you can perform=
 =
a full database export in Oracle.&nbsp; Many times it's quicker to restore =
=66rom an export.&nbsp; It's also a good way to go if you have multiple =
schemas in the database and want to only restore one of them.</FONT></P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Jon Walton [<A =
HREF=3D"mailto:jonw AT n2h2 DOT com">mailto:jonw AT n2h2 DOT com</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Thursday, May 09, 2002 6:57 AM</FONT>
<BR><FONT SIZE=3D2>To: Donaldson, Mark</FONT>
<BR><FONT SIZE=3D2>Cc: 'Mauro Palmiero'; =
veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2>Subject: RE: [Veritas-bu] pre-command and =
post-command</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Does Oracle have a built-in 'dump' command that performs =
a=
 database dump</FONT>
<BR><FONT SIZE=3D2>to a file or series of files?&nbsp;&nbsp;&nbsp; This is =
how we backup our Sybase ASE</FONT>
<BR><FONT SIZE=3D2>servers.&nbsp;&nbsp; We dump to a filer, then backup tha=
t=
 filer to tape after the</FONT>
<BR><FONT SIZE=3D2>database dump has finished.</FONT>
</P>

<P><FONT SIZE=3D2>Since the database dumps stay on the filer for a few days=
,=
 more often than</FONT>
<BR><FONT SIZE=3D2>not, the DBA can perform restores without any interactio=
n=
 with the</FONT>
<BR><FONT SIZE=3D2>backup/restore system.</FONT>
</P>

<P><FONT SIZE=3D2>Of course this method gets tougher and more expensive wit=
h=
 very large</FONT>
<BR><FONT SIZE=3D2>databases.</FONT>
</P>

<P><FONT SIZE=3D2>-Jon</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>On Thu, 9 May 2002, Donaldson, Mark wrote:</FONT>
</P>

<P><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; There's a couple of options with Oracle:</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; 1. Use RMAN - Oracle's internal backup tool.&nbsp; =
This takes another license</FONT>
<BR><FONT SIZE=3D2>&gt; ($$) from Veritas and Netbackup will basically =
provide little more then</FONT>
<BR><FONT SIZE=3D2>&gt; media services.&nbsp; It's nice if you want the =
DBA's fully managing the backups.</FONT>
<BR><FONT SIZE=3D2>&gt; It also allows incremental backups of Oracle files =
-=
 the only option to</FONT>
<BR><FONT SIZE=3D2>&gt; permit this.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; 2. Cold Backups - Shut down oracle and send the =
=66iles just using a regular</FONT>
<BR><FONT SIZE=3D2>&gt; file backup.&nbsp; You can do this with a =
pre-schedule job.&nbsp; See the</FONT>
<BR><FONT SIZE=3D2>&gt; bpstart_notify and bpend_notify descriptions in the=
 =
manual.&nbsp; In short, you</FONT>
<BR><FONT SIZE=3D2>&gt; can setup a class for the cold backup, then put the=
 =
Oracle shutdown in</FONT>
<BR><FONT SIZE=3D2>&gt; bpstart_notify.&lt;classname&gt; and the oracle =
restart in</FONT>
<BR><FONT SIZE=3D2>&gt; bpend_notify.&lt;classname&gt;.&nbsp; Note, you =
usually have to increase the wait times</FONT>
<BR><FONT SIZE=3D2>&gt; in the master server to allow enough time to get th=
e=
 DB down and up.&nbsp; See</FONT>
<BR><FONT SIZE=3D2>&gt; the bp.conf entries fo BPSTART_TIMEOUT and =
BPEND_TIMEOUT.&nbsp; The downside is</FONT>
<BR><FONT SIZE=3D2>&gt; the DB is out for the duration of the backup.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; 3. Rolling Hot backups - this is our internal term =
=66or this method.&nbsp; The</FONT>
<BR><FONT SIZE=3D2>&gt; technique here is using the user-backup feature of =
NB.&nbsp; (Note the DB has to</FONT>
<BR><FONT SIZE=3D2>&gt; be in log mode to successfully put a tablespace in =
hot-backup mode.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp; a. Query the database for all tablespac=
e=
 names </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp; b. For each tablespace, in =
sequence</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1. query oracle for =
datafiles related to the tablespace (place in a</FONT>
<BR><FONT SIZE=3D2>&gt; file)</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2. place tablespace i=
n=
 hot-backup mode</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3. use bpbackup to =
send the list of datafiles to netbackup</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 4. remove tablespace =
=66rom hot-backup mode</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 5. loop for next =
tablespace.</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp; c. Alter control file to trace and send=
 =
that file via bpbackup, too.</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp; d. Roll the redo logs - wait for =
completion.</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp; e. Send relavent archived redo log =
=66iles, this is the set that starts from</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; just before the first=
 =
tablespace is put into HB mode up to and</FONT>
<BR><FONT SIZE=3D2>&gt; including </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the last one that =
results from rolling the redo logs.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; This makes a whole bunch of NB images, one per =
tablespace, that represents a</FONT>
<BR><FONT SIZE=3D2>&gt; single backup of the entire database.&nbsp; To trac=
k=
 these as a set, we tie them</FONT>
<BR><FONT SIZE=3D2>&gt; together with a keyword based on backup date &amp; =
instance name.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Restoring is a pain, compared to a cold backup, =
because there's a lot of</FONT>
<BR><FONT SIZE=3D2>&gt; redo logs to apply to get to a time-consistent imag=
e=
 but it does work and</FONT>
<BR><FONT SIZE=3D2>&gt; the DB stays up all the time.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; 4. Yet another method is to do something expensive =
with split mirrors or</FONT>
<BR><FONT SIZE=3D2>&gt; BCV's but that's too big to detail here.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; If anyone has another method, let's hear about =
it.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; HTH - Mark</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Mauro Palmiero [<A =
HREF=3D"mailto:mpalmiero AT intin DOT it">mailto:mpalmiero AT intin DOT 
it</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Thursday, May 09, 2002 6:45 AM</FONT>
<BR><FONT SIZE=3D2>&gt; To: veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: [Veritas-bu] pre-command and =
post-command</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Hi,</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; I have a client with db oracle, I need to backup th=
e=
 db when It's stop, how</FONT>
<BR><FONT SIZE=3D2>&gt; can do It?</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Thank you.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; Veritas-bu maillist&nbsp; -&nbsp; =
Veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2>&gt; <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>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

<P><FONT SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Veritas-bu maillist&nbsp; -&nbsp; =
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>
<P>------------------------------------------------------------------------=
------<br>
<br>
<br>
This email is confidential and may be legally privileged.<br>
<br>
It is intended solely for the addressee. Access to this email by anyone =
else, unless expressly approved by the sender or an authorized addressee, i=
s=
 unauthorized.<br>
<br>
If you are not the intended recipient, any disclosure, copying, distributio=
n=
 or any action omitted or taken in reliance on it, is prohibited and may be=
 =
unlawful. If you believe that you have received this email in error, please=
 =
contact the sender, delete this e-mail and destroy all copies.<br>
<br>
<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D<br>
</P>

------_=_NextPart_001_01C1F764.E9B2E450--