Veritas-bu

[Veritas-bu] Upgraded to 5.1 and full windows 2003 restores do not work right?

2005-12-22 14:20:26
Subject: [Veritas-bu] Upgraded to 5.1 and full windows 2003 restores do not work right?
From: pens18aj AT yahoo DOT com (Andrew Johnson)
Date: Thu, 22 Dec 2005 11:20:26 -0800 (PST)
--0-1918072831-1135279226=:3192
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Ok,  We did open up a ticket with Veritas and they said going to MP4 would not 
fix us it should work now but does fix some restore issues on domain 
controllers.  I guess we will look at testing/upgrading again.
   
  But I am still wondering if you know of anything about how to restore a 
system to different hardware ? namely a system that has a different RAID 
controller than the original backup.  Actually, with Backup Exec, I don?t think 
there was that kind of documentation either.  We learned our trick from Sungard 
during our first test run with them.  The trick goes like this:
   
  -          If the original server had an HP NetRAID 1M controller then the 
driver restored from tape would be ?mraidnt.sys?.  And if the new hardware was 
a Compaq server with a Compaq Smart Array 5si controller, then the driver 
already on the system would be ?cpqcissm.sys?.
  -          In this example, ?cpqcissm.sys? on the basic hardware install 
would be copied and the copy renamed ?mraidnt.sys?.  This would now allow the 
restored registry to call the same file name so the system can load a working 
RAID driver.
  -          During the restore, the ?mraidnt.sys? on the backup tape will be 
excluded from restore.  This way the restored system will be using a RAID 
controller driver for the right hardware but it will have the name from the 
original system that was backed up.
  -          When the system came back up, we would run a full install of the 
normal RAID drivers to make sure everything functioned correctly from this 
point forward.
   
  This issue we have is that the ?system state? backup used to be drillable.  
We could drill down in the backup file structure and exclude the driver file as 
needed.  Now with VSS, that is no longer possible.  As we worked, we also found 
that this practice even worked well for systems moving to the same hardware.  
We had a much higher success rate of restoring systems when we were able to 
exclude the following files: boot.ini, ntdetect.com, ntldr, and the RAID 
controller driver (all these exclusions were recommended by Sungard from their 
experience with restoring windows systems to different hardware).  Only the 
boot.ini file is NOT protected ? the rest of the files are so they would be in 
that inaccessible VSS area.  Even if the RAID controller driver is for the same 
system, we still exclude it from the restore.  That way, we are using the most 
current driver (from the basic install of the system) for that RAID controller. 
 
   
  Following these steps has given us the highest success rate but if there is 
something else we can try, we are more than willing to test it out.  Thanks 
again for your help 

   
  Andrew
   
  
"Spearman, David" <spe08 AT co.henrico.va DOT us> wrote:
      Make sure you are at MP4 on the master/media and client. There was a 
major bug regarding full restores to w2k3 that was fixed.
   
  David Spearman IT
  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 Andrew Johnson
Sent: Thursday, December 22, 2005 10:11 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Upgraded to 5.1 and full windows 2003 restores do not 
work right?


  We just upgraded from 4.5 to 5.1 and we tried to do some restores of 2003 
servers like we did with 4.5 and are not having any luck.  The current 5.1 
client uses the volume shadow copy services (VSS) to do backups on Windows 2003 
machines.  We found that this makes things difficult when restoring a server ? 
especially when restoring to different hardware because certain protected files 
can no longer be selected/deselected as needed.
   
  We just tested a restore of an entire system to the same hardware (we backed 
the fully loaded system up, we wip! ed the system clean, we then installed the 
base OS along with the backup client, and we finally ran the restore).  The 
result was a system that will not even get to the windows GINA before 
bluescreening/rebooting continually.
   
  Is there any documentation on best practices for restoring an entire windows 
OS from scratch using NetBackup (as in a disaster recovery situation)?  
Likewise, is there any documentation and/or recommendation on restoring an 
entire system to different hardware?  We have successfully done restores of 
full systems from backups that still use the ?System State? method of 
addressing protected files (instead of VSS).  With that in mind, we would 
prefer a solution using what we have without! having to investigate something 
new like bare metal restores.  Any direction you can offer would be most 
appreciated.


  R. Andrew Johnson
  __________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


                
---------------------------------
Yahoo! Shopping
 Find Great Deals on Holiday Gifts at Yahoo! Shopping 
--0-1918072831-1135279226=:3192
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<div class=MsoNormal><FONT face=Arial color=navy size=2><SPAN style="FONT-SIZE: 
10pt; COLOR: navy; FONT-FAMILY: Arial">Ok,&nbsp; We did open up a ticket with 
Veritas and they said going to MP4 would not fix us it should work now but does 
fix some restore issues on domain controllers.&nbsp; I guess we will look at 
testing/upgrading again.</SPAN></FONT></div>  <div class=MsoNormal><FONT 
face=Arial color=navy size=2><SPAN style="FONT-SIZE: 10pt; COLOR: navy; 
FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</div>  <div class=MsoNormal><FONT 
face=Arial color=navy size=2><SPAN style="FONT-SIZE: 10pt; COLOR: navy; 
FONT-FAMILY: Arial">But I am still wondering if you know of anything about how 
to restore a system to different hardware ? namely a system that has a 
different RAID controller than the original backup.&nbsp; Actually, with Backup 
Exec, I don?t think there was that kind of documentation either.&nbsp; We 
learned our trick from Sungard during our first test run with them.&nbsp; The 
trick
 goes like this:<?xml:namespace prefix = o ns = 
"urn:schemas-microsoft-com:office:office" /><o:p></o:p></SPAN></FONT></div>  
<div class=MsoNormal><FONT face=Arial color=navy size=2><SPAN style="FONT-SIZE: 
10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p>&nbsp;</o:p></SPAN></FONT></div>  
<div class=MsoNormal style="MARGIN-LEFT: 0.5in; TEXT-INDENT: -0.25in"><FONT 
face=Arial color=navy size=2><SPAN style="FONT-SIZE: 10pt; COLOR: navy; 
FONT-FAMILY: Arial">-</SPAN></FONT><FONT color=navy size=1><SPAN 
style="FONT-SIZE: 7pt; COLOR: 
navy">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
</SPAN></FONT><FONT face=Arial color=navy size=2><SPAN style="FONT-SIZE: 10pt; 
COLOR: navy; FONT-FAMILY: Arial">If the original server had an HP NetRAID 1M 
controller then the driver restored from tape would be ?mraidnt.sys?.&nbsp; And 
if the new hardware was a Compaq server with a Compaq Smart Array 5si 
controller, then the driver already on the system would be 
?cpqcissm.sys?.<o:p></o:p></SPAN></FONT></div>
  <div class=MsoNormal style="MARGIN-LEFT: 0.5in; TEXT-INDENT: -0.25in"><FONT 
face=Arial color=navy size=2><SPAN style="FONT-SIZE: 10pt; COLOR: navy; 
FONT-FAMILY: Arial">-</SPAN></FONT><FONT color=navy size=1><SPAN 
style="FONT-SIZE: 7pt; COLOR: 
navy">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
</SPAN></FONT><FONT face=Arial color=navy size=2><SPAN style="FONT-SIZE: 10pt; 
COLOR: navy; FONT-FAMILY: Arial">In this example, ?cpqcissm.sys? on the basic 
hardware install would be copied and the copy renamed ?mraidnt.sys?.&nbsp; This 
would now allow the restored registry to call the same file name so the system 
can load a working RAID driver.<o:p></o:p></SPAN></FONT></div>  <div 
class=MsoNormal style="MARGIN-LEFT: 0.5in; TEXT-INDENT: -0.25in"><FONT 
face=Arial color=navy size=2><SPAN style="FONT-SIZE: 10pt; COLOR: navy; 
FONT-FAMILY: Arial">-</SPAN></FONT><FONT color=navy size=1><SPAN 
style="FONT-SIZE: 7pt; COLOR: 
navy">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 </SPAN></FONT><FONT face=Arial color=navy size=2><SPAN style="FONT-SIZE: 10pt; 
COLOR: navy; FONT-FAMILY: Arial">During the restore, the ?mraidnt.sys? on the 
backup tape will be excluded from restore.&nbsp; This way the restored system 
will be using a RAID controller driver for the right hardware but it will have 
the name from the original system that was backed 
up.<o:p></o:p></SPAN></FONT></div>  <div class=MsoNormal style="MARGIN-LEFT: 
0.5in; TEXT-INDENT: -0.25in"><FONT face=Arial color=navy size=2><SPAN 
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">-</SPAN></FONT><FONT 
color=navy size=1><SPAN style="FONT-SIZE: 7pt; COLOR: 
navy">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
</SPAN></FONT><FONT face=Arial color=navy size=2><SPAN style="FONT-SIZE: 10pt; 
COLOR: navy; FONT-FAMILY: Arial">When the system came back up, we would run a 
full install of the normal RAID drivers to make sure everything functioned 
correctly from this point
 forward.<o:p></o:p></SPAN></FONT></div>  <div class=MsoNormal><FONT face=Arial 
color=navy size=2><SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: 
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></div>  <div class=MsoNormal><FONT 
face=Arial color=navy size=2><SPAN style="FONT-SIZE: 10pt; COLOR: navy; 
FONT-FAMILY: Arial">This issue we have is that the ?system state? backup used 
to be drillable.&nbsp; We could drill down in the backup file structure and 
exclude the driver file as needed.&nbsp; Now with VSS, that is no longer 
possible.&nbsp; As we worked, we also found that this practice even worked well 
for systems moving to the same hardware.&nbsp; We had a much higher success 
rate of restoring systems when we were able to exclude the following files: 
boot.ini, ntdetect.com, ntldr, and the RAID controller driver (all these 
exclusions were recommended by Sungard from their experience with restoring 
windows systems to different hardware).&nbsp; Only the boot.ini file is NOT 
protected ? the
 rest of the files are so they would be in that inaccessible VSS area.&nbsp; 
Even if the RAID controller driver is for the same system, we still exclude it 
from the restore.&nbsp; That way, we are using the most current driver (from 
the basic install of the system) for that RAID controller.&nbsp; 
<o:p></o:p></SPAN></FONT></div>  <div class=MsoNormal><FONT face=Arial 
color=navy size=2><SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: 
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></div>  <div class=MsoNormal><FONT 
face=Arial color=navy size=2><SPAN style="FONT-SIZE: 10pt; COLOR: navy; 
FONT-FAMILY: Arial">Following these steps has given us the highest success rate 
but if there is something else we can try, we are more than willing to test it 
out.&nbsp; Thanks again for your help </SPAN></FONT><BR></div>  <div 
class=MsoNormal>&nbsp;</div>  <div class=MsoNormal>Andrew</div>  <div 
class=MsoNormal>&nbsp;</div>  <div class=MsoNormal><BR><B><I>"Spearman, David"
 &lt;spe08 AT co.henrico.va DOT us&gt;</I></B> wrote:</div>  <BLOCKQUOTE 
class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 
2px solid">  <META content="MSHTML 6.00.2900.2802" name=GENERATOR>  <DIV><SPAN 
class=401291016-22122005><FONT face=Arial color=#0000ff size=2>Make sure you 
are at MP4 on the master/media and client. There was a major bug regarding full 
restores to w2k3 that was fixed.</FONT></SPAN></DIV>  <DIV><SPAN 
class=401291016-22122005><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>  <DIV><SPAN class=401291016-22122005><FONT 
face=Arial color=#0000ff size=2>David Spearman IT</FONT></SPAN></DIV>  
<DIV><SPAN class=401291016-22122005><FONT face=Arial color=#0000ff 
size=2>County of Henrico, Va.</FONT></SPAN></DIV>  <BLOCKQUOTE dir=ltr 
style="MARGIN-RIGHT: 0px">  <DIV></DIV>  <DIV class=OutlookMessageHeader 
lang=en-us dir=ltr align=left><FONT face=Tahoma size=2>-----Original 
Message-----<BR><B>From:</B> veritas-bu-admin AT mailman.eng.auburn DOT edu
 [mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] <B>On Behalf Of 
</B>Andrew Johnson<BR><B>Sent:</B> Thursday, December 22, 2005 10:11 
AM<BR><B>To:</B> veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> 
[Veritas-bu] Upgraded to 5.1 and full windows 2003 restores do not work 
right?<BR><BR></FONT></DIV>  <DIV class=MsoNormal><FONT face=Arial size=2><SPAN 
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">We just upgraded from 4.5 to 5.1 
and we tried to do some restores of 2003 servers like we did with 4.5 and are 
not having any luck.&nbsp; The current 5.1 client uses the volume shadow copy 
services (VSS) to do backups on Windows 2003 machines.&nbsp; We found that this 
makes things difficult when restoring a server ? especially when restoring to 
different hardware because certain protected files can no longer be 
selected/deselected as needed.<o:p></o:p></SPAN></FONT></DIV>  <DIV 
class=MsoNormal><FONT face=Arial size=2><SPAN style="FONT-SIZE: 10pt; 
FONT-FAMILY:
 Arial"><o:p>&nbsp;</o:p></SPAN></FONT></DIV>  <DIV class=MsoNormal><FONT 
face=Arial size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">We just 
tested a restore of an entire system to the same hardware (we backed the fully 
loaded system up, we wip! ed the system clean, we then installed the base OS 
along with the backup client, and we finally ran the restore).&nbsp; The result 
was a system that will not even get to the windows GINA before 
bluescreening/rebooting continually.<o:p></o:p></SPAN></FONT></DIV>  <DIV 
class=MsoNormal><FONT face=Arial size=2><SPAN style="FONT-SIZE: 10pt; 
FONT-FAMILY: Arial"><o:p>&nbsp;</o:p></SPAN></FONT></DIV>  <DIV 
class=MsoNormal><FONT face=Arial size=2><SPAN style="FONT-SIZE: 10pt; 
FONT-FAMILY: Arial">Is there any documentation on best practices for restoring 
an entire windows OS from scratch using NetBackup (as in a disaster recovery 
situation)?&nbsp; Likewise, is there any documentation and/or recommendation on 
restoring an entire system to
 different hardware?&nbsp; We have successfully done restores of full systems 
from backups that still use the ?System State? method of addressing protected 
files (instead of VSS).&nbsp; With that in mind, we would prefer a solution 
using what we have without! having to investigate something new like bare metal 
restores.&nbsp; Any direction you can offer would be most 
appreciated.<o:p></o:p></SPAN></FONT></DIV><BR><BR>  <DIV><STRONG><FONT 
size=3><FONT color=#0000ff><FONT color=#ff0000>R.</FONT> <FONT 
color=#0000ff>Andrew </FONT></FONT><FONT color=#ff0000>Johnson<IMG 
src="http://us.i1.yimg.com/us.yimg.com/i/mesg/tsmileys2/14.gif"; 
NOSEND="1"></FONT></FONT></STRONG></DIV>  
<div>__________________________________________________<BR>Do You 
Yahoo!?<BR>Tired of spam? Yahoo! Mail has the best spam protection around 
<BR>http://mail.yahoo.com </div></BLOCKQUOTE></BLOCKQUOTE><BR><p>
                <hr size=1>Yahoo! Shopping<br> 
Find Great Deals on Holiday Gifts at <a 
href="http://us.rd.yahoo.com/mail_us/footer/shopping/*http://shopping.yahoo.com/;_ylc=X3oDMTE2bzVzaHJtBF9TAzk1OTQ5NjM2BHNlYwNtYWlsdGFnBHNsawNob2xpZGF5LTA1
 
">Yahoo! Shopping</a> 
--0-1918072831-1135279226=:3192--