Veritas-bu
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

FW: [Veritas-bu] Backuping Up Cluster 2003 Server

2005-11-08 12:17:59
Subject: FW: [Veritas-bu] Backuping Up Cluster 2003 Server
From: pkeating AT bank-banque-canada DOT ca (Paul Keating)
Date: Tue, 8 Nov 2005 12:17:59 -0500 
This is a multi-part message in MIME format.

------_=_NextPart_001_01C5E488.5DEF2430
Content-Type: text/plain;
        charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

=20
-----Original Message-----
From: Paul Keating=20
Sent: November 8, 2005 12:05 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Backuping Up Cluster 2003 Server


You can force the restore regardless of disk signature.
=20
from page 12 of the HA SAG.
=20
The cluster quorum is backed up as part of System State for each node.
To restore the cluster quorum, other nodes in the cluster must be
offline. If you cannot take the other nodes in the cluster offline
before restoring the cluster quorum, you can create the following
registry entry to force the restore of the cluster=20
=20
HKEY_LOCAL_MACHINE\Software\VERITAS\NetBackup\CurrentVersion\Config\
Cluster_Database_Force_Restore=20
        Note The actual registry entry above must be on a single line.=20
If required, create this registry value as data type REG_SZ with a value
of YES. When this value is set, the cluster service is stopped for any
nodes that are online.
=20
---snip---
=20
HERE'S THE IMPORTANT PART...
=20
If the disk where cluster quorum previously resided has been changed
(The disk could have been replaced with a new one, or the disk
configuration could have been changed so that the cluster quorum now
resides on a different disk.), you may have to set the registry entry
described above to force the restore to continue. This enables the drive
letter of the disk that the cluster quorum was on to remain the same,
even if the configuration has changed and the disk signatures contained
in the restore media do not match the disk signatures contained in the
cluster quorum.=20

        =20

        =20

        =20

        -----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 Spearman,
David
        Sent: November 8, 2005 11:05 AM
        To: BarberL AT mont.disa DOT mil; simon.weaver AT astrium.eads DOT net;
veritas-bu AT mailman.eng.auburn DOT edu
        Subject: RE: [Veritas-bu] Backuping Up Cluster 2003 Server
=09
=09
        All very true, which is way it's a good idea to run dumpcfg out
to a text file on all the nodes. (mine is on the root of all the nodes)
The dumpcfg command tells you what the drive signature of the external
drive(s) prior to the disaster. You can always pull the file from tape
if the cluster turns to slag. dumpcfg can also be used to modify the
signature on the new system.
        =20
        David Spearman
        County of Henrico, Va.

                -----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
BarberL AT mont.disa DOT mil
                Sent: Tuesday, November 08, 2005 10:45 AM
                To: simon.weaver AT astrium.eads DOT net;
BarberL AT mont.disa DOT mil; veritas-bu AT mailman.eng.auburn DOT edu
                Subject: RE: [Veritas-bu] Backuping Up Cluster 2003
Server
        =09
        =09
                Restoring data will work, but if you have to do a
complete DR and restore the entire cluster (server(s) and shared
volumes) from tape, the volume serials will be different (only need to
be the same on the shared volumes) if you reformat the existing shared
volumes or go to new shared volumes. Cluster software stores the vol
serials and will not come up if they do not match. (Make sense?)


------_=_NextPart_001_01C5E488.5DEF2430
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></FONT>&nbsp;</DIV>
<DIV></DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT face=3DTahoma=20
size=3D2>-----Original Message-----<BR><B>From:</B> Paul Keating =
<BR><B>Sent:</B>=20
November 8, 2005 12:05 PM<BR><B>To:</B>=20
veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> RE: [Veritas-bu] =
Backuping=20
Up Cluster 2003 Server<BR><BR></FONT></DIV>
<DIV><SPAN class=3D334010117-08112005><FONT face=3DArial color=3D#800000 =
size=3D2>You=20
can force the restore regardless of disk signature.</FONT></SPAN></DIV>
<DIV><SPAN class=3D334010117-08112005><FONT face=3DArial color=3D#800000 =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D334010117-08112005><FONT face=3DArial color=3D#800000 =
size=3D2>from=20
page 12 of the HA SAG.</FONT></SPAN></DIV>
<DIV><FONT face=3DArial><FONT size=3D2><FONT color=3D#800000><FONT =
face=3DArial><FONT=20
size=3D2><SPAN class=3D334010117-08112005><FONT face=3DArial=20
size=3D2></FONT></SPAN></FONT></FONT></FONT></FONT></FONT>&nbsp;</DIV><FO=
NT=20
face=3DArial><FONT size=3D2><SPAN class=3D334010117-08112005><FONT =
face=3DPalatino-Roman=20
size=3D2>
<DIV>The cluster quorum is backed up as part of System State for each =
node. To=20
restore the cluster quorum, other nodes in the cluster must be offline. =
If you=20
cannot take the other nodes in the cluster offline before restoring the =
cluster=20
quorum, you can create the following registry entry to force the restore =
of the=20
cluster </DIV></FONT>
<DIV><FONT color=3D#800000><FONT=20
color=3D#800000></FONT></FONT>&nbsp;</DIV></SPAN></FONT></FONT><SPAN=20
class=3D334010117-08112005><FONT face=3DArial size=3D2>
<DIV>HKEY_LOCAL_MACHINE\Software\VERITAS\NetBackup\CurrentVersion\Config\=
=20
Cluster_Database_Force_Restore </DIV></FONT>
<DIV><FONT face=3DArial><FONT size=3D2><SPAN=20
class=3D334010117-08112005>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</SPAN>Note=20
The actual registry entry above must be on a single line. =
</FONT></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>If required, create this registry value =
as data=20
type REG_SZ with a value of YES. When this value is set, the cluster =
service is=20
stopped for any nodes that are online.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D334010117-08112005><FONT face=3DArial=20
size=3D2>---snip---</FONT></SPAN></DIV>
<DIV><SPAN class=3D334010117-08112005><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D334010117-08112005><FONT face=3DArial =
size=3D2><STRONG>HERE'S THE=20
IMPORTANT PART...</STRONG></FONT></SPAN></DIV>
<DIV><SPAN class=3D334010117-08112005><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D334010117-08112005><FONT face=3DPalatino-Roman><FONT =
face=3DArial=20
color=3D#800000 size=3D2><FONT color=3D#000000><EM>If the disk where =
cluster quorum=20
previously resided has been changed (The disk could have been replaced =
with a=20
new one, or the disk configuration could have been changed so that the =
cluster=20
quorum now resides on a different disk.), you may have to set the =
registry entry=20
described above to force the restore to continue. This enables the drive =
letter=20
of the disk that the cluster quorum was on to remain the same, even if =
the=20
configuration has changed and the disk signatures contained in the =
restore media=20
do not match the disk signatures contained in the cluster =
quorum.</EM></FONT>=20
</FONT></DIV>
<DIR></FONT>
<P><FONT face=3DArial color=3D#800000 size=3D2></FONT>&nbsp;</P>
<P><FONT face=3DArial color=3D#800000 size=3D2></FONT>&nbsp;</P></SPAN>
<P><FONT face=3DArial color=3D#800000 =
size=3D2></FONT>&nbsp;</P></DIR></SPAN>
<BLOCKQUOTE dir=3Dltr=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 =
</B>Spearman,=20
  David<BR><B>Sent:</B> November 8, 2005 11:05 AM<BR><B>To:</B>=20
  BarberL AT mont.disa DOT mil; simon.weaver AT astrium.eads DOT net;=20
  veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> RE: 
[Veritas-bu]=20
  Backuping Up Cluster 2003 Server<BR><BR></FONT></DIV>
  <DIV><SPAN class=3D383170016-08112005><FONT face=3DArial =
color=3D#0000ff size=3D2>All=20
  very true, which is way it's a good idea to run dumpcfg out to a text =
file on=20
  all the nodes.&nbsp;(mine is on the root of all the nodes) The dumpcfg =
command=20
  tells you what the drive signature of the external drive(s) prior to =
the=20
  disaster. You can always pull the file from tape if the cluster turns =
to slag.=20
  dumpcfg can also be used to modify the signature on the new=20
  system.</FONT></SPAN></DIV>
  <DIV><SPAN class=3D383170016-08112005><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D383170016-08112005><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>David Spearman</FONT></SPAN></DIV>
  <DIV><SPAN class=3D383170016-08112005><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>County of Henrico, Va.</FONT></SPAN></DIV>
  <BLOCKQUOTE dir=3Dltr style=3D"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>BarberL AT mont.disa DOT mil<BR><B>Sent:</B> Tuesday, November 08, 2005 
=
10:45=20
    AM<BR><B>To:</B> simon.weaver AT astrium.eads DOT net; =
BarberL AT mont.disa DOT mil;=20
    veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> RE: =
[Veritas-bu]=20
    Backuping Up Cluster 2003 Server<BR><BR></FONT></DIV>
    <DIV><SPAN class=3D433194215-08112005><FONT face=3DArial =
color=3D#0000ff=20
    size=3D2>Restoring data will work, but if you have to do a complete =
DR and=20
    restore the entire cluster (server(s) and shared volumes)&nbsp;from =
tape,=20
    the volume serials will be different (only need to be the same on =
the shared=20
    volumes) if you reformat the existing shared volumes or go to new =
shared=20
    volumes. Cluster software stores the vol serials and will not come =
up if=20
    they do not match. (Make=20
sense?)</FONT></SPAN></DIV></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>
=00
------_=_NextPart_001_01C5E488.5DEF2430--
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  [Veritas-bu] Multiple data stream and bpend_notify script, Peter DrakeUnderkoffler
Next by Date:  [Veritas-bu] RE: How to troubleshoot a Firewall Client Backup with Clustered Netbackup Server, Kilpatrick, Mark
Previous by Thread:  [Veritas-bu] Backuping Up Cluster 2003 Server, Spearman, David
Next by Thread:  [Veritas-bu] Duplication Problem, praveen sundriyal
Indexes:  [Date] [Thread] [Top] [All Lists]