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_01C48B9E.B3202B20
Content-Type: text/plain;
charset="iso-8859-1"
I've successfully restored many NT 4.0 servers the way you describe with one
exception - after installing the OS, I apply the latest service pack and all
security updates released as of the last successful incremental backup prior to
starting the restore. Haven't had the opportunity to test with Windows server
2000 or 2003 yet...
Neil
-----Original Message-----
From: French, Michael [mailto:Michael.French AT savvis DOT net]
Sent: Wednesday, August 25, 2004 11:53 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Windows 2003 restore questions
Site info:
Netbackup 4.5FP6
Solaris 8 master and media servers
Windows 2003 enterprise edition clients with 4.5FP6 nbu client
installed
No Veritas BMR server
We're having a problem at my company getting Netbackup to successfully
restore a complete Windows 2003 server. We have had several servers die
recently and the restores have not worked as expected. When the systems have
died, we have installed a fresh version of the OS, put it on the network, left
it in a workgroup, and installed the NBU client. A full restore is done of the
C:\ drive and the system state from the last full backup and all of the diffs
in between. The server goes into a continual reboot cycle after the restore
completes and we restart the server.
I've been doing some testing and have gotten it to work if I do the
restore with just the last full backup image (C:\ and system state), reboot,
then apply the diffs for C:\ and the latest system state. I also used the
command:
w2koption -restore -same_hardware 1
This command was used both before the restore started and after it
completed. At this point, it would successfully boot. This seems pretty
cumbersome. How is everyone else out in NBU land doing this?
One other way I got this to work was to do a complete restore of C:\,
full and diffs, with no system state, and then use a dump of the system state
that was created by ntbackup. The machine successfully boots at this point.
Michael French
Savvis Communications
Enterprise Storage Engineer
(314)628-7392 -- desk
(408)239-9913 -- mobile
------_=_NextPart_001_01C48B9E.B3202B20
Content-Type: text/html;
charset="iso-8859-1"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>Windows 2003 restore questions</TITLE>
<META content="MSHTML 6.00.2900.2180" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=928105118-26082004>I've
successfully restored many NT 4.0 servers the way you describe with one
exception - after installing the OS, I apply the latest service pack
and all security updates released as of the last successful incremental
backup prior to starting the restore. Haven't had the
opportunity to test with Windows server 2000 or 2003
yet...</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=928105118-26082004></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=928105118-26082004>Neil</SPAN></FONT></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> French, Michael
[mailto:Michael.French AT savvis DOT net]<BR><B>Sent:</B> Wednesday, August
25, 2004
11:53 AM<BR><B>To:</B> veritas-bu AT mailman.eng.auburn DOT
edu<BR><B>Subject:</B>
[Veritas-bu] Windows 2003 restore questions<BR><BR></FONT></DIV>
<P> <FONT face=Arial size=2>Site
info:</FONT> </P>
<P> <FONT face=Arial
size=2>Netbackup 4.5FP6</FONT> <BR>
<FONT face=Arial size=2>Solaris 8 master and media servers</FONT>
<BR> <FONT face=Arial
size=2>Windows
2003 enterprise edition clients with 4.5FP6 nbu client installed</FONT>
<BR> <FONT face=Arial size=2>No
Veritas BMR server</FONT> </P>
<P> <FONT face=Arial size=2>We're
having a problem at my company getting Netbackup to successfully restore a
complete Windows 2003 server. We have had several servers die recently
and the restores have not worked as expected. When the systems have
died, we have installed a fresh version of the OS, put it on the network,
left
it in a workgroup, and installed the NBU client. A full restore is done
of the C:\ drive and the system state from the last full backup and all of
the
diffs in between. The server goes into a continual reboot cycle after
the restore completes and we restart the server.</FONT></P>
<P> <FONT face=Arial size=2>I've
been doing some testing and have gotten it to work if I do the restore with
just the last full backup image (C:\ and system state), reboot, then apply
the
diffs for C:\ and the latest system state. I also used the
command:</FONT></P>
<P><FONT face=Arial size=2>w2koption -restore -same_hardware 1</FONT> </P>
<P> <FONT face=Arial size=2>This
command was used both before the restore started and after it
completed.
At this point, it would successfully boot. This seems pretty
cumbersome. How is everyone else out in NBU land doing this?</FONT></P>
<P> <FONT face=Arial size=2>One
other way I got this to work was to do a complete restore of C:\, full and
diffs, with no system state, and then use a dump of the system state that was
created by ntbackup. The machine successfully boots at this
point.</FONT></P>
<P><FONT face=Arial color=#0000ff size=2>Michael French</FONT> <BR><FONT
face=Arial color=#0000ff size=2>Savvis Communications</FONT> <BR><FONT
face=Arial color=#0000ff size=2>Enterprise Storage Engineer</FONT> <BR><FONT
face=Arial color=#0000ff size=2>(314)628-7392 -- desk</FONT> <BR><FONT
face=Arial color=#0000ff size=2>(408)239-9913 -- mobile</FONT> <BR><B><FONT
face=Arial> </FONT></B> </P></BLOCKQUOTE></BODY></HTML>
------_=_NextPart_001_01C48B9E.B3202B20--
|
