Veritas-bu

[Veritas-bu] Veritas NBU DR - any clues ?

2002-10-10 10:16:01
Subject: [Veritas-bu] Veritas NBU DR - any clues ?
From: Steve.White AT PacifiCorp DOT com (White, Steve)
Date: Thu, 10 Oct 2002 07:16:01 -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_01C27067.8FAC95B0
Content-Type: text/plain;
 charset=iso-8859-1
Content-Transfer-Encoding: 7bit

My that's a wide-open question :-)

Here's some high level thoughts, and some pointers.

For creating the duplicates, you can set it up manually, you can use some of
the scripts folks like David Chappa has written and published to the
advanced scripting web site, or you can implement the Vault extension.  If
your environment is moderately complex or you're running NBU 4.5, then I'd
go with Vault.  It's a pretty good way to manage duplicating and offsite
vaulting of tapes.

Obviously you'll need to make sure a copy of your NetBackup catalog backup
is going offsite with your regular offsite tapes.

Chapter 5 of the "NetBackup Troubleshooting Guide" (at least for version
3.4) contains some pretty good examples of D/R scenarios, along with
step-by-step processes to bring your catalog back from tape.  Here are some
other thoughts along that line:

1.  When you're arranging your D/R environment, if at all possible, have the
hardware be a similar setup to your production site.  That will make
rebuilding the NBU environment easier.  Another thing is that I've found it
easiest if your D/R server(s) can use the same names as the production
servers, otherwise you'll need to do some work with the bp.conf file to
force the restores to look for the D/R server rather than the production
server.

2.  What I typically do when running a D/R scenario, is to install the NBU
binaries, then restore the catalog backups.  Once I've done that, I
configure the tape drives, robots, and storage units to appropriately
reflect the D/R environment.  Then I bring up the NBU daemons.

3.  If your catalog is so large that you have to use the "two stage" catalog
backup process, then what you'll need to do is restore the catalog backup
created with "bpbackupdb" which will restore the image files for the master
server, then after you have NBU running on the master, you'll need to do a
standard file restore of the rest of the images database.

4.  Since you're using duplicates rather than originals, you'll need to
promote the duplicate images to be the primary copy using the "bpimage -npc"
command for all the images you need to restore from.

The rest is pretty straight-forward in terms of installing the clients and
starting the restores.

-----Original Message-----
From: Sharma, Dayanand (CAP, GEFA, Contractor)
[mailto:Dayanand.Sharma AT gecapital DOT com]
Sent: Monday, October 07, 2002 5:44 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Veritas NBU DR - any clues ?



Hi

I am looking for some precise steps on restoration in a DR scenario using
duplicated tapes, including creation of duplicate tapes. Our production
tapes are highly multiplexed.  Any pointers any one ?

Thanks in Advance !
Dayanand
_______________________________________________
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_01C27067.8FAC95B0
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] Veritas NBU DR - any clues ?</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>My that's a wide-open question :-)</FONT>
</P>

<P><FONT SIZE=3D2>Here's some high level thoughts, and some pointers.</FONT>
</P>

<P><FONT SIZE=3D2>For creating the duplicates, you can set it up manually, =
you can use some of the scripts folks like David Chappa has written and =
published to the advanced scripting web site, or you can implement the Vaul=
t=
 extension.&nbsp; If your environment is moderately complex or you're =
running NBU 4.5, then I'd go with Vault.&nbsp; It's a pretty good way to =
manage duplicating and offsite vaulting of tapes.</FONT></P>

<P><FONT SIZE=3D2>Obviously you'll need to make sure a copy of your =
NetBackup catalog backup is going offsite with your regular offsite =
tapes.</FONT></P>

<P><FONT SIZE=3D2>Chapter 5 of the &quot;NetBackup Troubleshooting =
Guide&quot; (at least for version 3.4) contains some pretty good examples o=
=66=
 D/R scenarios, along with step-by-step processes to bring your catalog bac=
k=
 from tape.&nbsp; Here are some other thoughts along that line:</FONT></P>

<P><FONT SIZE=3D2>1.&nbsp; When you're arranging your D/R environment, if a=
t=
 all possible, have the hardware be a similar setup to your production =
site.&nbsp; That will make rebuilding the NBU environment easier.&nbsp; =
Another thing is that I've found it easiest if your D/R server(s) can use =
the same names as the production servers, otherwise you'll need to do some =
work with the bp.conf file to force the restores to look for the D/R server=
 =
rather than the production server.</FONT></P>

<P><FONT SIZE=3D2>2.&nbsp; What I typically do when running a D/R scenario,=
 =
is to install the NBU binaries, then restore the catalog backups.&nbsp; Onc=
e=
 I've done that, I configure the tape drives, robots, and storage units to =
appropriately reflect the D/R environment.&nbsp; Then I bring up the NBU =
daemons.</FONT></P>

<P><FONT SIZE=3D2>3.&nbsp; If your catalog is so large that you have to use=
 =
the &quot;two stage&quot; catalog backup process, then what you'll need to =
do is restore the catalog backup created with &quot;bpbackupdb&quot; which =
will restore the image files for the master server, then after you have NBU=
 =
running on the master, you'll need to do a standard file restore of the res=
t=
 of the images database.</FONT></P>

<P><FONT SIZE=3D2>4.&nbsp; Since you're using duplicates rather than =
originals, you'll need to promote the duplicate images to be the primary =
copy using the &quot;bpimage -npc&quot; command for all the images you need=
 =
to restore from.</FONT></P>

<P><FONT SIZE=3D2>The rest is pretty straight-forward in terms of installin=
g=
 the clients and starting the restores.</FONT>
</P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Sharma, Dayanand (CAP, GEFA, Contractor)</FONT>
<BR><FONT SIZE=3D2>[<A =
HREF=3D"mailto:Dayanand.Sharma AT gecapital DOT 
com">mailto:Dayanand.Sharma@gecapi=
tal.com</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Monday, October 07, 2002 5:44 PM</FONT>
<BR><FONT SIZE=3D2>To: veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2>Subject: [Veritas-bu] Veritas NBU DR - any clues ?</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>Hi</FONT>
</P>

<P><FONT SIZE=3D2>I am looking for some precise steps on restoration in a D=
R=
 scenario using</FONT>
<BR><FONT SIZE=3D2>duplicated tapes, including creation of duplicate tapes.=
 =
Our production</FONT>
<BR><FONT SIZE=3D2>tapes are highly multiplexed.&nbsp; Any pointers any one=
 =
?</FONT>
</P>

<P><FONT SIZE=3D2>Thanks in Advance !</FONT>
<BR><FONT SIZE=3D2>Dayanand</FONT>
<BR><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_01C27067.8FAC95B0--


<Prev in Thread] Current Thread [Next in Thread>