This is a multi-part message in MIME format.
------_=_NextPart_001_01C5F5AD.D204FA6D
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
or just stop NBU, unmount /opt/openv on the master, create a new slice,
mount it as /opt/openv and install and bprecover on the new slice.
-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Dean
Sent: November 30, 2005 3:21 AM
To: WEAVER, Simon
Cc: veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] Netbackup Broke - Possible Way Out and
Require Opinions
=09
=09
I would not mess with the production "working" master server.
Wiping out your active catalog on purpose and relying on bprecover to
get it back sounds ... risky. Not that I've ever seen bprecover fail,
but I believe in NOT tempting fate.=20
=09
Is it possible to have a 'spare' server sitting around, with the
same OS and hostname as the production master, but not registered in
your DNS, or not normally connected to the LAN at all? bprecover your
pre-problems catalog to it and just let it sit there until it's needed.
It wouldn't need to be too powerful. Then if a restore is required,
update /etc/hosts on the client (or the Windows equivelant) to point to
your "standby" master server, do the restore, then undo the /etc/hosts
change. I've seen this done with an old Ultra 5, and even on a VMware
guest machine.
=09
Of course, you'd also need a tape drive connected to this
"standby" master if/when you need it for a restore.
=09
=09
------_=_NextPart_001_01C5F5AD.D204FA6D
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Message</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1170" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial color=3D#800000 size=3D2><SPAN =
class=3D934025812-30112005>or=20
just stop NBU, unmount /opt/openv on the master, create a new slice, =
mount it as=20
/opt/openv and install and bprecover on the new =
slice.</SPAN></FONT></DIV>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #800000 2px =
solid; MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT=20
face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B>=20
veritas-bu-admin AT mailman.eng.auburn DOT edu=20
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] <B>On Behalf Of=20
</B>Dean<BR><B>Sent:</B> November 30, 2005 3:21 AM<BR><B>To:</B> =
WEAVER,=20
Simon<BR><B>Cc:</B> =
veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> Re:=20
[Veritas-bu] Netbackup Broke - Possible Way Out and Require=20
Opinions<BR><BR></FONT></DIV>I would not mess with the production =
"working"=20
master server. Wiping out your active catalog on purpose and relying =
on=20
bprecover to get it back sounds ... risky. Not that I've ever seen =
bprecover=20
fail, but I believe in NOT tempting fate. <BR><BR>Is it possible to =
have a=20
'spare' server sitting around, with the same OS and hostname as the =
production=20
master, but not registered in your DNS, or not normally connected to =
the LAN=20
at all? bprecover your pre-problems catalog to it and just let it sit =
there=20
until it's needed. It wouldn't need to be too powerful. Then if a =
restore is=20
required, update /etc/hosts on the client (or the Windows equivelant) =
to point=20
to your "standby" master server, do the restore, then undo the =
/etc/hosts=20
change. I've seen this done with an old Ultra 5, and even on a VMware =
guest=20
machine.<BR><BR>Of course, you'd also need a tape drive connected to =
this=20
"standby" master if/when you need it for a=20
restore.<BR><BR></BLOCKQUOTE></BODY></HTML>
=00
------_=_NextPart_001_01C5F5AD.D204FA6D--
|
