Veritas-bu

[Veritas-bu] Windows 2003 restore questions

2004-08-25 14:52:35
Subject: [Veritas-bu] Windows 2003 restore questions
From: Michael.French AT savvis DOT net (French, Michael)
Date: Wed, 25 Aug 2004 13:52:35 -0500
This is a multi-part message in MIME format.

------_=_NextPart_001_01C48AD4.AFC01D0F
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

        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
=20


------_=_NextPart_001_01C48AD4.AFC01D0F
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.6980.59">
<TITLE>Windows 2003 restore questions</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">Site info:</FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">Netbackup 4.5FP6</FONT>

<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">Solaris 8 master and media servers</FONT>

<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">Windows 2003 enterprise edition clients with 4.5FP6 nbu =
client installed</FONT>

<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">No Veritas BMR server</FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">We're having a problem at my company getting Netbackup to =
successfully restore a complete Windows 2003 server.&nbsp; We have had =
several servers die recently and the restores have not worked as =
expected.&nbsp; 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.&nbsp; 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.&nbsp; The server goes into a continual reboot cycle after the =
restore completes and we restart the server.</FONT></P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">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.&nbsp; I also used the command:</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">w2koption -restore -same_hardware =
1</FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">This command was used both before the restore started and =
after it completed.&nbsp; At this point, it would successfully =
boot.&nbsp; This seems pretty cumbersome.&nbsp; How is everyone else out =
in NBU land doing this?</FONT></P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">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.&nbsp; The machine =
successfully boots at this point.</FONT></P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Michael French</FONT>

<BR><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Savvis =
Communications</FONT>

<BR><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Enterprise Storage =
Engineer</FONT>

<BR><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">(314)628-7392 -- =
desk</FONT>

<BR><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">(408)239-9913 -- =
mobile</FONT>

<BR><B><FONT FACE=3D"Arial">=A0</FONT></B>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C48AD4.AFC01D0F--

<Prev in Thread] Current Thread [Next in Thread>