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_01C331C4.9494B2F0
Content-Type: text/plain;
charset="iso-8859-1"
My DBA's tell me that the shutdown/startup commands are part of the RMAN
command set.
So, for an RMAN multistream cold you should be able to shutdown the DB,
create a multi-channel backup job via RMAN which translates to a NB
multistream backup, then startup the DB when complete. Call the RMAN script
from cron on the client & it's one shutdown & one startup.
-M
-----Original Message-----
From: Markham, Richard [mailto:RMarkham AT hafeleamericas DOT com]
Sent: Friday, June 13, 2003 8:42 AM
To: 'Donaldson, Mark'; List, VERITAS NBU
Subject: RE: [Veritas-bu] NBU/RMAN Cold Backup question
This thread struck a bit of curiousity in me. I haven't actually
implemented
"cold" backups through RMAN and NB. So the jobs themselves are sending
startup/shutdown commands to the db as it sees fit? Or do I have this
wrong?
Are the multiple jobs running the same main scripts each time, which contain
the startup/shutdown commands? Thanks for any heads up.
-----Original Message-----
From: Donaldson, Mark [ mailto:Mark.Donaldson AT experianems DOT com
<mailto:Mark.Donaldson AT experianems DOT com> ]
Sent: Wednesday, June 11, 2003 3:06 PM
To: Steven L. Sesar; List, VERITAS NBU
Subject: RE: [Veritas-bu] NBU/RMAN Cold Backup question
The first job to complete will probably attempt to bring the DB back up,
too.
You have to write a stream-aware set of scripts for DB startup & shutdown.
I do mine with a series of lock files & counters. The number of streams is
an environment variable & so I have a lockfile. For startup, each stream
checks for the lock file, creating it & starting the DB preparation if it is
the first to start. The loser of the race starts to watch for a completion
flag that the first stream will write when the DB is all the way down - then
they stop waiting & end to allow the backup to proceed.
The end-job is pretty much the same in reverse. The last stream to complete
has to restart the DB.
One quick way around this, since you've got RMAN is drop the Netbackup
scheduling & run the job from cron on the DB client. It's all driven from
RMAN script that way.
HTH - Mark
-----Original Message-----
From: Steven L. Sesar [ mailto:ssesar AT mitre DOT org <mailto:ssesar AT mitre
DOT org> ]
Sent: Wednesday, June 11, 2003 8:24 AM
To: List, VERITAS NBU
Subject: [Veritas-bu] NBU/RMAN Cold Backup question
Hi,
When I kick off a cold backup, NBU breaks the backup up into several
jobs. The problem with this, is that each new job that starts, tries to
shutdown/startup mount the SID that it is backing up.
Has anyone else encountered this, and what have you done about it?
NBU 4.5MP4, Solaris 8.
--Steve
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
<http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu>
------_=_NextPart_001_01C331C4.9494B2F0
Content-Type: text/html;
charset="iso-8859-1"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>RE: [Veritas-bu] NBU/RMAN Cold Backup question</TITLE>
<META content="MSHTML 5.50.4926.2500" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=325575515-13062003><FONT face=Arial color=#0000ff size=2>My
DBA's tell me that the shutdown/startup commands are part of the RMAN command
set.</FONT></SPAN></DIV>
<DIV><SPAN class=325575515-13062003><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=325575515-13062003><FONT face=Arial color=#0000ff size=2>So,
for an RMAN multistream cold you should be able to shutdown the DB, create a
multi-channel backup job via RMAN which translates to a NB multistream backup,
then startup the DB when complete. Call the RMAN script from cron on the
client & it's one shutdown & one startup.</FONT></SPAN></DIV>
<DIV><SPAN class=325575515-13062003><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=325575515-13062003><FONT face=Arial color=#0000ff
size=2>-M</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> Markham, Richard
[mailto:RMarkham AT hafeleamericas DOT com]<BR><B>Sent:</B> Friday, June 13,
2003
8:42 AM<BR><B>To:</B> 'Donaldson, Mark'; List, VERITAS NBU<BR><B>Subject:</B>
RE: [Veritas-bu] NBU/RMAN Cold Backup question<BR><BR></FONT></DIV>
<P><FONT size=2>This thread struck a bit of curiousity in me. I haven't
actually implemented </FONT><BR><FONT size=2>"cold" backups through RMAN and
NB. So the jobs themselves are sending </FONT><BR><FONT
size=2>startup/shutdown commands to the db as it sees fit? Or do I have
this wrong?</FONT> <BR><FONT size=2>Are the multiple jobs running the same
main scripts each time, which contain</FONT> <BR><FONT size=2>the
startup/shutdown commands? Thanks for any heads up.</FONT> </P><BR>
<P><FONT size=2>-----Original Message-----</FONT> <BR><FONT size=2>From:
Donaldson, Mark [<A
href="mailto:Mark.Donaldson AT experianems DOT com">mailto:Mark.Donaldson AT
experianems DOT com</A>]</FONT>
<BR><FONT size=2>Sent: Wednesday, June 11, 2003 3:06 PM</FONT> <BR><FONT
size=2>To: Steven L. Sesar; List, VERITAS NBU</FONT> <BR><FONT
size=2>Subject:
RE: [Veritas-bu] NBU/RMAN Cold Backup question</FONT> </P><BR>
<P><FONT size=2>The first job to complete will probably attempt to bring the
DB back up,</FONT> <BR><FONT size=2>too.</FONT> </P>
<P><FONT size=2>You have to write a stream-aware set of scripts for DB
startup
& shutdown.</FONT> </P>
<P><FONT size=2>I do mine with a series of lock files & counters.
The number of streams is</FONT> <BR><FONT size=2>an environment variable
&
so I have a lockfile. For startup, each stream</FONT> <BR><FONT
size=2>checks for the lock file, creating it & starting the DB
preparation
if it is</FONT> <BR><FONT size=2>the first to start. The loser of the
race starts to watch for a completion</FONT> <BR><FONT size=2>flag that the
first stream will write when the DB is all the way down - then</FONT>
<BR><FONT size=2>they stop waiting & end to allow the backup to
proceed.</FONT> </P>
<P><FONT size=2>The end-job is pretty much the same in reverse. The
last
stream to complete</FONT> <BR><FONT size=2>has to restart the DB.</FONT> </P>
<P><FONT size=2>One quick way around this, since you've got RMAN is drop the
Netbackup</FONT> <BR><FONT size=2>scheduling & run the job from
cron
on the DB client. It's all driven from</FONT> <BR><FONT size=2>RMAN
script that way.</FONT> </P>
<P><FONT size=2>HTH - Mark</FONT> </P>
<P><FONT size=2>-----Original Message-----</FONT> <BR><FONT size=2>From:
Steven L. Sesar [<A
href="mailto:ssesar AT mitre DOT org">mailto:ssesar AT mitre DOT
org</A>]</FONT> <BR><FONT
size=2>Sent: Wednesday, June 11, 2003 8:24 AM</FONT> <BR><FONT size=2>To:
List, VERITAS NBU</FONT> <BR><FONT size=2>Subject: [Veritas-bu] NBU/RMAN Cold
Backup question</FONT> </P><BR>
<P><FONT size=2>Hi,</FONT> </P>
<P><FONT size=2>When I kick off a cold backup, NBU breaks the backup up into
several </FONT><BR><FONT size=2>jobs. The problem with this, is that each new
job that starts, tries to </FONT><BR><FONT size=2>shutdown/startup mount the
SID that it is backing up.</FONT> <BR><FONT size=2> </FONT> <BR><FONT
size=2>Has anyone else encountered this, and what have you done about
it?</FONT> </P>
<P><FONT size=2>NBU 4.5MP4, Solaris 8.</FONT> </P>
<P><FONT size=2>--Steve</FONT> </P>
<P><FONT size=2>_______________________________________________</FONT>
<BR><FONT size=2>Veritas-bu maillist -
Veritas-bu AT mailman.eng.auburn DOT edu</FONT> <BR><FONT size=2><A
target=_blank
href="http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu";>http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu</A></FONT>
</P></BLOCKQUOTE></BODY></HTML>
------_=_NextPart_001_01C331C4.9494B2F0--
|
