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_01C42B9E.AF75C03D
Content-Type: text/plain
When you perform the restore. We found that it is best practice to delete
the network cards and video cards from Device Manager prior to the post
restore reboot. (ie immediately after the restore completes) We also
re-apply the proper HAL prior to that first reboot.
Also do not restore the veritas and veritas shared directories.
Not sure if this helps.
_____________________________________________
From: veritas-bu-admin AT mailman.eng.auburn DOT edu@AICI On Behalf Of Mark
Steel
<mark AT steelfamily DOT org>
Sent: Monday, April 26, 2004 10:29 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Win2K System state restore onto different hardware
All
I'm trying to restore Win2k server to a spare machine - different name,
different hardware ( ie like a real DR ). No BMR ( too expensive ).
The restore gose ok, then reboot the DR machine and it comes up almost to
login, then reboots, and continues that cycle.
We think its hardware/driver related but cannot narrow it down. We current
have the default windows registry apart from:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\BackupRestore\KeysNotToR
estore
where InstalledServices is blank ( to allow restore of all services ).
Any thoughts on what to do/not do ?
regards
Mark
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
CONFIDENTIALITY NOTICE: This e-mail message, including any attachments,
is for the sole use of the intended recipient(s) and may contain confidential
and privileged information or otherwise protected by law. Any unauthorized
review, use, disclosure or distribution is prohibited. If you are not the
intended recipient, please contact the sender by reply e-mail and destroy
all copies of the original message.
------_=_NextPart_001_01C42B9E.AF75C03D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Dus-asci=
i">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version 5.5.2657.7=
3">
<TITLE>RE: [Veritas-bu] Win2K System state restore onto different hardwar=
e</TITLE>
</HEAD>
<BODY>
<P ALIGN=3DLEFT><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">When you =
perform the restore. We found that it is best practice to delete th=
e network cards and video cards from Device Manager prior to the post res=
tore reboot. (ie immediately after the restore completes) We =
also re-apply the proper HAL prior to that first reboot.</FONT></P>
<P ALIGN=3DLEFT><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Also do n=
ot restore the veritas and veritas shared directories.</FONT></P>
<P ALIGN=3DLEFT><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Not sure =
if this helps.</FONT></P>
<P ALIGN=3DLEFT><FONT SIZE=3D2 FACE=3D"Tahoma">__________________________=
___________________<BR>
</FONT><B></B><B><FONT SIZE=3D2 FACE=3D"Tahoma">From:</FONT></B><FONT SIZ=
E=3D2 FACE=3D"Tahoma"> veritas-bu-admin AT mailman.eng.auburn DOT
edu@AICI</FONT=
><B></B><B> <FONT SIZE=3D2 FACE=3D"Tahoma">On Behalf Of</FONT></B> <FONT =
SIZE=3D2 FACE=3D"Tahoma">Mark Steel <mark AT steelfamily DOT org><BR>
</FONT><B></B><B><FONT SIZE=3D2 FACE=3D"Tahoma">Sent:</FONT></B><FONT SIZ=
E=3D2 FACE=3D"Tahoma"> Monday, April 26, 2004 10:29 AM<BR>
</FONT><B></B><B><FONT SIZE=3D2 FACE=3D"Tahoma">To:</FONT></B><FONT SIZE=3D=
2 FACE=3D"Tahoma"> veritas-bu AT mailman.eng.auburn DOT edu<BR>
</FONT><B></B><B><FONT SIZE=3D2 FACE=3D"Tahoma">Subject:</FONT></B><FONT =
SIZE=3D2 FACE=3D"Tahoma"> [Veritas-bu] Win2K System state restore onto di=
fferent hardware</FONT></P>
<P ALIGN=3DLEFT><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Courier">All</FO=
NT></P>
<P ALIGN=3DLEFT><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Courier">I'm try=
ing to restore Win2k server to a spare machine - different name,</FONT></=
P>
<P ALIGN=3DLEFT><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Courier">differe=
nt hardware ( ie like a real DR ). No BMR ( too expensive ).</FONT></P>
<P ALIGN=3DLEFT><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Courier">The res=
tore gose ok, then reboot the DR machine and it comes up almost to</FONT>=
</P>
<P ALIGN=3DLEFT><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Courier">login, =
then reboots, and continues that cycle.</FONT></P>
<P ALIGN=3DLEFT><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Courier">We thin=
k its hardware/driver related but cannot narrow it down. We current</FONT=
></P>
<P ALIGN=3DLEFT><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Courier">have th=
e default windows registry apart from:</FONT></P>
<P ALIGN=3DLEFT><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Courier">HKEY_LO=
CAL_MACHINE\SYSTEM\CurrentControlSet\Control\BackupRestore\KeysNotToResto=
re</FONT></P>
<P ALIGN=3DLEFT><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Courier">where I=
nstalledServices is blank ( to allow restore of all services ).</FONT></P=
>
<P ALIGN=3DLEFT><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Courier">Any tho=
ughts on what to do/not do ?</FONT></P>
<P ALIGN=3DLEFT><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Courier">regards=
</FONT></P>
<P ALIGN=3DLEFT><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Courier">Mark</F=
ONT></P>
<BR>
<BR>
<P ALIGN=3DLEFT><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Courier">_______=
________________________________________</FONT></P>
<P ALIGN=3DLEFT><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Courier">Veritas=
-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu</FONT></P>
<P ALIGN=3DLEFT><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Courier"><A HREF=
=3D"http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu"; TARGET=3D"=
_blank">http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu</A></FO=
NT></P>
</BODY>
</HTML>
<BR>
CONFIDENTIALITY NOTICE: This e-mail message, including any attachments,=20
is for the sole use of the intended recipient(s) and may contain confiden=
tial
and privileged information or otherwise be protected by law. Any unautho=
rized
review, use, disclosure or distribution is prohibited. If you are not th=
e
intended recipient, please contact the sender by reply e-mail and destroy
all copies of the original message.
------_=_NextPart_001_01C42B9E.AF75C03D--
|
