This is a multi-part message in MIME format.
------_=_NextPart_001_01C5BDFD.2BE9DC0D
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
I turned TIR on once because a consultant said to get a true image you
have to have that on. I turned it off because I couldn't get to the
files level on the restore screen. We do a lot of individual file
restores it seems. I read the manual, of course, and can see that it
makes sense for rebuilding a whole server but couldn't really see using
for our situation. I'd be interested in hearing from other people that
use it and why.=20
=20
I haven't looked into IDR so I'd be interested in hearing about that as
well. To recover or rebuild a server, we install the OS ,
maintenance/service pack, and apps, install NetBackup client, then
restore data. On Windows we would restore the system drive and system
state with overwrite. I believe that's how it would work but I haven't
been asked to do this yet. The only server I've ever rebuilt is the
Veritas Master server, on Solaris 8.
________________________________
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Piszcz,
Justin
Sent: Monday, September 19, 2005 5:02 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Best attributes for backup?
All,
=20
How many here use the following options..?
[x] Collect true image restore information.
[x] with move detection.
[x] Collect disaster recover information.
=20
I know using TIR causes problems with some Solaris machines. Windows
machines do not seem to have many problems with enabling these. =20
=20
As far as DR, it would appear particularly useful, however, one question
about D/R. If a machine dies and you replace it with a clone but say a
few things differ, HDD sizes or NIC or chipset, would this affect the
full restoration of a box?
=20
About the DR Files
The disaster recovery (DR) files are mentioned frequently in this
chapter and in the
screens that you see in the wizards. A DR file contains specific
information about the
computer you are protecting, including:
* Hard disk partition information.
* Network interface card information.
* NetBackup configuration information required to restore data files.
To fully automate the recovery of an IDR-protected computer, you need a
copy of the DR
file for that computer. If IDR software is installed on the server and
client and the server is
configured to collect disaster recovery information, NetBackup creates a
DR file and stores
a copy on the client and the master server after every:
* Full backup
* Incremental (differential or cumulative) backup
* User backup
* User archive
NetBackup stores the DR file for each client in the
install_path\NetBackup\Idr\
data directory on the client. The DR files generated after a backup are
named in the
format netbackup_client_name.dr. For example, if the client name is
bison, the DR
file is bison.dr.
Note IDR requires that the DR file name match the computer name of the
client. That is, if
the computer name is recognized by the network as bison, then the DR
file must be
named bison.dr. If the NetBackup client name is different for some
reason, you
must manually rename a DR file created after each backup to
computer_name.dr
before you can use it in a recovery.
On the NetBackup master server, the DR files for all clients are stored
in the NetBackup
catalogs on the server.
=20
=20
=20
------_=_NextPart_001_01C5BDFD.2BE9DC0D
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40"; xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.2722" name=3DGENERATOR>
<STYLE>@font-face {
font-family: Courier;
}
@font-face {
font-family: ZapfDingbats;
}
@font-face {
font-family: Helvetica-Bold;
}
@font-face {
font-family: Palatino-Roman;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
COLOR: windowtext; FONT-FAMILY: Arial; mso-style-type: personal-compose
}
DIV.Section1 {
page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D027104315-20092005><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>I turned TIR on once because a consultant said =
to get a=20
true image you have to have that on. I turned it off because I =
couldn't=20
get to the files level on the restore screen. We do a lot of =
individual=20
file restores it seems. I read the manual, of course, and can see =
that it=20
makes sense for rebuilding a whole server but couldn't really see =
using for=20
our situation. I'd be interested in hearing from other people that =
use it=20
and why. </FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D027104315-20092005><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN> </DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D027104315-20092005><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>I haven't looked into IDR so I'd be interested =
in hearing=20
about that as well. To recover or rebuild a server, we =
install the OS=20
, maintenance/service pack, and apps, install NetBackup client, then =
restore=20
data. On Windows we would restore the system drive and =
system=20
state with overwrite. I believe that's how it would work but I =
haven't=20
been asked to do this yet. The only server I've ever rebuilt is =
the=20
Veritas Master server, on Solaris 8.</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> =
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>Piszcz,=20
Justin<BR><B>Sent:</B> Monday, September 19, 2005 5:02 AM<BR><B>To:</B>=20
veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> [Veritas-bu] Best=20
attributes for backup?<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=3DSection1>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">All,<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">How many here use the =
following=20
options..?<BR><BR><o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">[x] Collect true image =
restore=20
information.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"> [x] =
with move=20
detection.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">[x] Collect disaster =
recover=20
information.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">I know using TIR causes =
problems=20
with some Solaris machines. Windows machines do not seem to have =
many=20
problems with enabling these. <o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">As far as DR, it would =
appear=20
particularly useful, however, one question about D/R. If a machine =
dies=20
and you replace it with a clone but say a few things differ, HDD sizes =
or NIC or=20
chipset, would this affect the full restoration of a=20
box?<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><B><FONT face=3DHelvetica-Bold size=3D5><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 16pt; FONT-FAMILY: =
Helvetica-Bold">About=20
the DR Files<o:p></o:p></SPAN></FONT></B></P>
<P class=3DMsoNormal><FONT face=3DPalatino-Roman size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Palatino-Roman">The disaster =
recovery (DR)=20
files are mentioned frequently in this chapter and in=20
the<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DPalatino-Roman size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Palatino-Roman">screens that you =
see in the=20
wizards. A DR file contains specific information about=20
the<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DPalatino-Roman size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Palatino-Roman">computer you are=20
protecting, including:<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DZapfDingbats size=3D1><SPAN=20
style=3D"FONT-SIZE: 9pt; FONT-FAMILY: ZapfDingbats">◆ =
</SPAN></FONT><FONT=20
face=3DPalatino-Roman size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Palatino-Roman">Hard disk =
partition=20
information.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DZapfDingbats size=3D1><SPAN=20
style=3D"FONT-SIZE: 9pt; FONT-FAMILY: ZapfDingbats">◆ =
</SPAN></FONT><FONT=20
face=3DPalatino-Roman size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Palatino-Roman">Network interface =
card=20
information.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DZapfDingbats size=3D1><SPAN=20
style=3D"FONT-SIZE: 9pt; FONT-FAMILY: ZapfDingbats">◆ =
</SPAN></FONT><FONT=20
face=3DPalatino-Roman size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Palatino-Roman">NetBackup =
configuration=20
information required to restore data files.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DPalatino-Roman size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Palatino-Roman">To fully automate =
the=20
recovery of an IDR-protected computer, you need a copy of the=20
DR<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DPalatino-Roman size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Palatino-Roman">file for that =
computer. If=20
IDR software is installed on the server and client and the server=20
is<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DPalatino-Roman size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Palatino-Roman">configured to =
collect=20
disaster recovery information, NetBackup creates a DR file and=20
stores<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DPalatino-Roman size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Palatino-Roman">a copy on the =
client and=20
the master server after every:<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DZapfDingbats size=3D1><SPAN=20
style=3D"FONT-SIZE: 9pt; FONT-FAMILY: ZapfDingbats">◆ =
</SPAN></FONT><FONT=20
face=3DPalatino-Roman size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Palatino-Roman">Full=20
backup<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DZapfDingbats size=3D1><SPAN=20
style=3D"FONT-SIZE: 9pt; FONT-FAMILY: ZapfDingbats">◆ =
</SPAN></FONT><FONT=20
face=3DPalatino-Roman size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Palatino-Roman">Incremental =
(differential=20
or cumulative) backup<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DZapfDingbats size=3D1><SPAN=20
style=3D"FONT-SIZE: 9pt; FONT-FAMILY: ZapfDingbats">◆ =
</SPAN></FONT><FONT=20
face=3DPalatino-Roman size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Palatino-Roman">User=20
backup<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DZapfDingbats size=3D1><SPAN=20
style=3D"FONT-SIZE: 9pt; FONT-FAMILY: ZapfDingbats">◆ =
</SPAN></FONT><FONT=20
face=3DPalatino-Roman size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Palatino-Roman">User=20
archive<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DPalatino-Roman size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Palatino-Roman">NetBackup stores =
the DR=20
file for each client in the </SPAN></FONT><FONT face=3DCourier =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Courier">install_path\NetBackup\Idr\<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DCourier size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Courier">data </SPAN></FONT><FONT =
face=3DPalatino-Roman size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Palatino-Roman">directory on the =
client.=20
The DR files generated after a backup are named in=20
the<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DPalatino-Roman size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Palatino-Roman">format =
</SPAN></FONT><FONT=20
face=3DCourier size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Courier">netbackup_client_name.dr</SPAN></FONT><FONT=20
face=3DPalatino-Roman size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Palatino-Roman">. For example, if =
the=20
client name is bison, the DR<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DPalatino-Roman size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Palatino-Roman">file is =
</SPAN></FONT><FONT=20
face=3DCourier size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Courier">bison.dr</SPAN></FONT><FONT=20
face=3DPalatino-Roman size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Palatino-Roman">.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><B><FONT face=3DHelvetica-Bold size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Helvetica-Bold">Note=20
</SPAN></FONT></B><FONT face=3DPalatino-Roman size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Palatino-Roman">IDR requires that =
the DR=20
file name match the computer name of the client. That is,=20
if<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DPalatino-Roman size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Palatino-Roman">the computer name =
is=20
recognized by the network as bison, then the DR file must=20
be<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DPalatino-Roman size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Palatino-Roman">named =
</SPAN></FONT><FONT=20
face=3DCourier size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Courier">bison.dr</SPAN></FONT><FONT=20
face=3DPalatino-Roman size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Palatino-Roman">. If the =
NetBackup client=20
name is different for some reason, you<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DPalatino-Roman size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Palatino-Roman">must manually =
rename a DR=20
file created after each backup to </SPAN></FONT><FONT face=3DCourier =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Courier">computer_name.dr<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DPalatino-Roman size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Palatino-Roman">before you can =
use it in a=20
recovery.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DPalatino-Roman size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Palatino-Roman">On the NetBackup =
master=20
server, the DR files for all clients are stored in the=20
NetBackup<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DPalatino-Roman size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Palatino-Roman">catalogs on the=20
server.</SPAN></FONT><FONT face=3DHelvetica-Bold size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Helvetica-Bold"><o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p> </o:p></SPAN></FONT></P></DIV></BODY></HTML>
------_=_NextPart_001_01C5BDFD.2BE9DC0D--
|
