I must confess that it has been a while since I have performed a W2K BMR and
although I have always just copied back the files post restore for W2K3 BMR's,
I had recalled that this was not possible in W2K as some of the files were held
exclusively by the OS.
However, finding a W2K machine, I can now see that this is not the case and it
is definitely far easier to just copy the files back immediately after the
restore for both and only use the recovery console/in-place upgrade in the
event of a failed boot.
I think that in some quarters, Wintel BMR's are seen as a 'fine art' or in some
way not standard or excessively problematic. Hopefully Geoff, you will have
gained some confidence in that there are many people who have performed a high
number of Wintel BMR's without incident. I think there will always be the
occasional exception and this would be true of the other platforms and OS's. I
still think that performing a DR trial of your business critical Wintel systems
on a regular basis gives the greatest piece of mind.
One typo in my original posting, it should have read
For Windows2003, they are as follows
c:\windows\system32\hal.dll
c:\windows\system32\ntkrnlpa.exe
c:\windows\system32\ntoskrnl.exe
Leigh
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
TSM_User
Sent: 28 September 2006 02:09
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [SPAM: 9.000] Re: [ADSM-L] BMR - unlike hardware
While the recovery console could be used you can also choose to copy the files
out, perform the restore and then copy the files back before you reboot. You
only need to use the RC if you forget to copy the files back before you reboot.
I've posted the use of the "in-place" upgrade many times to ensure the new
hardware on the new server is properly enumerated. Still, I always use the
approach of copying out the files and then back in after the restore first.
With windows 2000 I've found this works about 80% of the time, with Windows
2003 almost 95% of the time. For the time when it doesn't work the "in-place"
upgrade does. For that process you do not have to use the RC at all to copy any
files first.
Kyle
Leigh Reed <L.Reed AT MDX.AC DOT UK> wrote:
Geoff
In my mind, the MS Recovery Console is the key to achieving successful
restores back to dissimilar h/w in the Wintel area. After installing
your vanilla MS OS (that is to be restored over), you need to take a
copy of the OS files that are specific to your h/w. Then, if they are
overwritten with different versions by your restore, you can put them
back with the RC upon reboot.
These files can be found in Device Manager--> Computer and then under
the driver details of the Properties of your processor(s).
For Windows2000, they are as follows
c:\winnt\system32\hal.dll
c:\winnt\system32\kernel32.dll
c:\winnt\system32\ntdll.dll
c:\winnt\system32\ntkrnlpa.exe
c:\winnt\system32\ntoskrnl.exe
c:\winnt\system32\win32k.sys
c:\winnt\system32\winsrv.dll
For Windows2003, they are as follows
c:\windows\system32\hal.dll
c:\winnt\system32\ntkrnlpa.exe
c:\winnt\system32\ntoskrnl.exe
If after you complete the restore of your system drive and you reboot
and get a blue screen or worse, all is not lost. The Microsoft Recovery
Console is an extremely useful tool. From the RC, you can copy the above
original files from a floppy or the root of the system drive to the
system32 directory. Also, the RC will enable you to disable devices or
services on boot.
One important point to note, the RC requires the LOCAL administrator
password to be entered before it can be used, therefore ensure that you
know the local passwords to all your machines.
The following IBM Technote is also very useful for Wintel system
restores
http://www-1.ibm.com/support/docview.wss?rs=663&context=SSGSG7&q1=116481
2&uid=swg21164812&loc=en_US&cs=utf-8&lang=en
Above all else, the key to restoring back to dissimilar h/w is practice.
Where possible, try to trial restore as many of your Wintel systems back
to unlike h/w. I know it is obvious, but it is far easier to solve any
arising issues in a DR trial environment, than at 3am with somebody
looking over your shoulder, asking every 5 minutes when will it be ready
?
Leigh
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Gill, Geoffrey L.
Sent: 23 September 2006 00:15
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [SPAM: 4.000] Re: [ADSM-L] BMR - unlike hardware
>What kind of system are you concerned with?
I'm looking for some basic info on all platforms anyone has experience
with,
Windows being the biggest concern. After hearing some remarks this
morning
in a meeting concerning bringing back a server from scratch, and how
long it
took, I'm flabbergasted. Then again nobody called me to ask for help
either.
To add to this are there any issues anyone is aware of for servers that
have
been virtualized but still use TSM for their backups? Would the process
be
the same?
Thanks,
Geoff Gill
TSM Administrator
PeopleSoft Sr. Systems Administrator
SAIC M/S-G1b
(858)826-4062
Email: geoffrey.l.gill AT saic DOT com
---------------------------------
Yahoo! Messenger with Voice. Make PC-to-Phone Calls to the US (and 30+
countries) for 2¢/min or less.
|
