Veritas-bu

[Veritas-bu] Backuping Up Cluster 2003 Server

2005-11-08 11:05:01
Subject: [Veritas-bu] Backuping Up Cluster 2003 Server
From: spe08 AT co.henrico.va DOT us (Spearman, David)
Date: Tue, 8 Nov 2005 11:05:01 -0500
This is a multi-part message in MIME format.

------_=_NextPart_001_01C5E47E.2CC0B66B
Content-Type: text/plain;
        charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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

                -----Original Message-----
                From: WEAVER, Simon
[mailto:simon.weaver AT astrium.eads DOT net]=20
                Sent: Tuesday, November 08, 2005 09:37 AM
                To: '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
                Well this is my sort of DR plan in the event of a
failure
                =20
                1 x restore Server from disk image (taken on a regular
basis)
                1 x restore the Data from Netbackup to the Virtual
Friendly names
                =20
                As a precaution, I also have been taking backups of the
CLUSTER named C: drives and system state!
                =20
                As long as the Data can be restored, I would have
thought this would work?

                Simon=20

                        -----Original Message-----
                        From: BarberL AT mont.disa DOT mil
[mailto:BarberL AT mont.disa DOT mil]=20
                        Sent: 08 November 2005 15:31
                        To: WEAVER, Simon;
veritas-bu AT mailman.eng.auburn DOT edu
                        Subject: RE: [Veritas-bu] Backuping Up Cluster
2003 Server
                =09
                =09
                        Just remember, If you have a disaster on a
cluster and do a DR, the volume serial numbers for each volume must be
the same after the DR as they were when backed up, or the cluster will
not come up. There is a tool from M$ that will allow you to get this
info and change to serial numbers as needed. We always had to document
the serials and keep a copy of the doc offsite as well as on site.

                                -----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 WEAVER,
Simon
                                Sent: Tuesday, November 08, 2005 09:01
AM
                                To: veritas-bu AT mailman.eng.auburn DOT edu
                                Subject: [Veritas-bu] Backuping Up
Cluster 2003 Server
                        =09
                        =09
                                Hi again
                                Does anyone have any experience on
backing up a cluster with NBU 5.x ?
                                =20
                                I have a question that I would like to
get confirmed as being the correct answer, in the event of problems
restoring the cluster!
                                =20
                                Basic setup
                                =20
                                Windows 2003 Server Cluster is known as
CLUSTER01. The Nodes are known as Cluster02 and Cluster03 as physical
computer names. On top of this, they also have "Virtual Names" known to
the users as "Data" and "Personal"
                                =20
                                At the moment, I have the Netbackup
client installed on Cluster02 and Cluster03 (As this is the physical
computer names of the Servers).
                                =20
                                Now, what I have been doing is
performing backups using the "Virtual Names". This has been working
fine, without too many issues.
                                =20
                                However, my question is this: Should I
also be doing backups of the Physical Computer Names or not?
                                =20
                                Not knowing clustering that well, I was
not entirely sure if this is the correct process, but it does work!
                                =20
                                Would be grateful for any information on
this. I want to be 100% sure that in the event of a disaster, I can
safely recover the node or worse case, the entire cluster.
                                =20
                                Thanks for any comments
                                =20
                                Simon
This email is for the intended addressee only.
If you have received it in error then you must not use, retain,
disseminate or otherwise deal with it.
Please notify the sender by return email.
The views of the author may not necessarily constitute the views of EADS
Astrium Limited.
Nothing in this email shall bind EADS Astrium Limited in any contract or
obligation.

EADS Astrium Limited, Registered in England and Wales No. 2449259
Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS,
England
=09

This email is for the intended addressee only.
If you have received it in error then you must not use, retain,
disseminate or otherwise deal with it.
Please notify the sender by return email.
The views of the author may not necessarily constitute the views of EADS
Astrium Limited.
Nothing in this email shall bind EADS Astrium Limited in any contract or
obligation.

EADS Astrium Limited, Registered in England and Wales No. 2449259
Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS,
England
=09


------_=_NextPart_001_01C5E47E.2CC0B66B
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.2900.2769" name=3DGENERATOR></HEAD>
<BODY>
<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 =

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 =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D383170016-08112005><FONT face=3DArial color=3D#0000ff =
size=3D2>David=20
Spearman</FONT></SPAN></DIV>
<DIV><SPAN class=3D383170016-08112005><FONT face=3DArial color=3D#0000ff =
size=3D2>County=20
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; =

  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, the=20
  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 they=20
  do not match. (Make sense?)</FONT></SPAN></DIV>
  <BLOCKQUOTE 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> =
WEAVER, Simon=20
    [mailto:simon.weaver AT astrium.eads DOT net] <BR><B>Sent:</B> Tuesday, =
November=20
    08, 2005 09:37 AM<BR><B>To:</B> '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=3D392333415-08112005><FONT face=3DArial =
color=3D#0000ff=20
    size=3D2>Well this is my sort of DR plan in the event of a=20
    failure</FONT></SPAN></DIV>
    <DIV><SPAN class=3D392333415-08112005><FONT face=3DArial =
color=3D#0000ff=20
    size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV><SPAN class=3D392333415-08112005><FONT face=3DArial =
color=3D#0000ff size=3D2>1=20
    x restore Server from&nbsp;disk image (taken on a regular=20
    basis)</FONT></SPAN></DIV>
    <DIV><SPAN class=3D392333415-08112005><FONT face=3DArial =
color=3D#0000ff size=3D2>1=20
    x restore the Data from Netbackup to the Virtual Friendly=20
    names</FONT></SPAN></DIV>
    <DIV><SPAN class=3D392333415-08112005><FONT face=3DArial =
color=3D#0000ff=20
    size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV><SPAN class=3D392333415-08112005><FONT face=3DArial =
color=3D#0000ff size=3D2>As=20
    a precaution, I also have been taking backups of the CLUSTER named =
C: drives=20
    and system state!</FONT></SPAN></DIV>
    <DIV><SPAN class=3D392333415-08112005><FONT face=3DArial =
color=3D#0000ff=20
    size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV><SPAN class=3D392333415-08112005><FONT face=3DArial =
color=3D#0000ff size=3D2>As=20
    long as the Data can be restored, I would have thought this would=20
    work?</FONT></SPAN></DIV><!-- Converted from text/rtf format -->
    <P><SPAN lang=3Den-gb><B><FONT face=3DArial color=3D#0000ff =
size=3D2>Simon=20
    </FONT></B></SPAN></P>
    <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
      BarberL AT mont.disa DOT mil [mailto:BarberL AT mont.disa DOT mil] =
<BR><B>Sent:</B> 08=20
      November 2005 15:31<BR><B>To:</B> WEAVER, Simon;=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=3D465582815-08112005><FONT face=3DArial =
color=3D#0000ff=20
      size=3D2>Just remember, If you have a disaster on a cluster and do =
a DR, the=20
      volume serial numbers for each volume must be the same after the =
DR as=20
      they were when backed up, or the cluster will not come up. There =
is a tool=20
      from M$ that will allow you to get this info and change to serial =
numbers=20
      as needed. We always had to document the serials and keep a copy =
of the=20
      doc offsite as well as on site.</FONT></SPAN></DIV>
      <BLOCKQUOTE 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 
=

        </B>WEAVER, Simon<BR><B>Sent:</B> Tuesday, November 08, 2005 =
09:01=20
        AM<BR><B>To:</B> =
veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B>=20
        [Veritas-bu] Backuping Up Cluster 2003 =
Server<BR><BR></FONT></DIV>
        <DIV><SPAN class=3D892405014-08112005><FONT face=3DArial =
size=3D2>Hi=20
        again</FONT></SPAN></DIV>
        <DIV><SPAN class=3D892405014-08112005><FONT face=3DArial =
size=3D2>Does anyone=20
        have any experience on backing up a cluster with NBU 5.x=20
        ?</FONT></SPAN></DIV>
        <DIV><SPAN class=3D892405014-08112005><FONT face=3DArial=20
        size=3D2></FONT></SPAN>&nbsp;</DIV>
        <DIV><SPAN class=3D892405014-08112005><FONT face=3DArial =
size=3D2>I have a=20
        question that I would like to get confirmed as being the correct =
answer,=20
        in the event of problems restoring the =
cluster!</FONT></SPAN></DIV>
        <DIV><SPAN class=3D892405014-08112005><FONT face=3DArial=20
        size=3D2></FONT></SPAN>&nbsp;</DIV>
        <DIV><SPAN class=3D892405014-08112005><FONT face=3DArial =
size=3D2>Basic=20
        setup</FONT></SPAN></DIV>
        <DIV><SPAN class=3D892405014-08112005><FONT face=3DArial=20
        size=3D2></FONT></SPAN>&nbsp;</DIV>
        <DIV><SPAN class=3D892405014-08112005><FONT face=3DArial =
size=3D2>Windows 2003=20
        Server Cluster is known as CLUSTER01. The Nodes are known as =
Cluster02=20
        and Cluster03 as physical computer names. On top of this, they =
also have=20
        "Virtual Names" known to the users as "Data" and=20
        "Personal"</FONT></SPAN></DIV>
        <DIV><SPAN class=3D892405014-08112005><FONT face=3DArial=20
        size=3D2></FONT></SPAN>&nbsp;</DIV>
        <DIV><SPAN class=3D892405014-08112005><FONT face=3DArial =
size=3D2>At the=20
        moment, I have the Netbackup client installed on Cluster02 and =
Cluster03=20
        (As this is the physical computer names of the=20
        Servers).</FONT></SPAN></DIV>
        <DIV><SPAN class=3D892405014-08112005><FONT face=3DArial=20
        size=3D2></FONT></SPAN>&nbsp;</DIV>
        <DIV><SPAN class=3D892405014-08112005><FONT face=3DArial =
size=3D2>Now, what I=20
        have been doing is performing backups using the "Virtual Names". =
This=20
        has been working fine, without too many =
issues.</FONT></SPAN></DIV>
        <DIV><SPAN class=3D892405014-08112005><FONT face=3DArial=20
        size=3D2></FONT></SPAN>&nbsp;</DIV>
        <DIV><SPAN class=3D892405014-08112005><FONT face=3DArial =
size=3D2>However, my=20
        question is this: Should I also be doing backups of the Physical =

        Computer Names or not?</FONT></SPAN></DIV>
        <DIV><SPAN class=3D892405014-08112005><FONT face=3DArial=20
        size=3D2></FONT></SPAN>&nbsp;</DIV>
        <DIV><SPAN class=3D892405014-08112005><FONT face=3DArial =
size=3D2>Not knowing=20
        clustering that well, I was not entirely sure if this is the =
correct=20
        process, but it does work!</FONT></SPAN></DIV>
        <DIV><SPAN class=3D892405014-08112005><FONT face=3DArial=20
        size=3D2></FONT></SPAN>&nbsp;</DIV>
        <DIV><SPAN class=3D892405014-08112005><FONT face=3DArial =
size=3D2>Would be=20
        grateful for any information on this. I want to be 100% sure =
that in the=20
        event of a disaster, I can safely recover the node or worse =
case, the=20
        entire cluster.</FONT></SPAN></DIV>
        <DIV><SPAN class=3D892405014-08112005><FONT face=3DArial=20
        size=3D2></FONT></SPAN>&nbsp;</DIV>
        <DIV><SPAN class=3D892405014-08112005><FONT face=3DArial =
size=3D2>Thanks for=20
        any comments</FONT></SPAN></DIV>
        <DIV><SPAN class=3D892405014-08112005><FONT face=3DArial=20
        size=3D2></FONT></SPAN>&nbsp;</DIV>
        <DIV><SPAN class=3D892405014-08112005><FONT face=3DArial=20
        size=3D2>Simon</FONT></SPAN></DIV>
        <TABLE>
          <TBODY>
          <TR>
            <TD bgColor=3D#ffffff><FONT color=3D#000000>This email is =
for the=20
              intended addressee only.<BR>If you have received it in =
error then=20
              you must not use, retain, disseminate or otherwise deal =
with=20
              it.<BR>Please notify the sender by return email.<BR>The =
views of=20
              the author may not necessarily constitute the views of =
EADS=20
              Astrium Limited.<BR>Nothing in this email shall bind EADS =
Astrium=20
              Limited in any contract or obligation.<BR><BR>EADS Astrium =

              Limited, Registered in England and Wales No. =
2449259<BR>Registered=20
              Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 =
2AS,=20
              =
England<BR></FONT></TD></TR></TBODY></TABLE></BLOCKQUOTE></BLOCKQUOTE>
    <TABLE>
      <TBODY>
      <TR>
        <TD bgColor=3D#ffffff><FONT color=3D#000000>This email is for =
the intended=20
          addressee only.<BR>If you have received it in error then you =
must not=20
          use, retain, disseminate or otherwise deal with it.<BR>Please =
notify=20
          the sender by return email.<BR>The views of the author may not =

          necessarily constitute the views of EADS Astrium =
Limited.<BR>Nothing=20
          in this email shall bind EADS Astrium Limited in any contract =
or=20
          obligation.<BR><BR>EADS Astrium Limited, Registered in England =
and=20
          Wales No. 2449259<BR>Registered Office: Gunnels Wood Road, =
Stevenage,=20
          Hertfordshire, SG1 2AS,=20
  =
England<BR></FONT></TD></TR></TBODY></TABLE></BLOCKQUOTE></BLOCKQUOTE></B=
ODY></HTML>

------_=_NextPart_001_01C5E47E.2CC0B66B--