Mehdi,
as John and Kelly pointed out you've missed juggling with the registry
and boot.ini. If I correctly noted you're doing a DR between dissimular
(did I spell that right otherwise is't spelled D.I.F.F.E.R.E.N.T)
hardware, the most difficult DR scenario to handle.
First up, you won't be able to use the original systems system registry
hive (the part where the systems hardware configuration is stored).
You'll have to copy the DR partitions system hive to the DR restored
NT partition (you can use regrest/regback or a registry export/import
utility to handle this).
Second up, there is a dependacy between the type NTOSKRNL.EXE and the
hardware it is installed on. The NTOSKRNL of a certain type multiple
processor motherboard can differ from the NTOSKRNL of a certain type
single processor board (this also goes for some types of bus differences
between boards AGP,PCI,MCA etc.) So when dealing with non matching
hardware copy the NTOSKRNL of the installed WINNT DR partition to the DR
restored partition.
Third up, if the DR systems (the system being restored to) has SCSI
(RAID) disk controller not recognized during standard NT installation
then after two reboots you'll get the blue screen of death. Up to a
certain point in NT installation NT can work with the generic INT13
BIOS disk calls to handle disk I/O. After that point NT drops the INT13
support and wants to work directly with the controller. So if no driver
support is loaded for the controller you'll get a 'can't boot from disk'
The only sollution for this is get the controller's driver installed
during NT setup.
And fourth, if the restored to partition logically differs from the
original WINNT partition location you'll have to edit the boot.ini to
point to the correct WINNT location.
Are you still brave enough, if so
then if you've covered the controller driver install, done a complete
system restore (root, WINNT & registry hives, the whole lot) of the DR'd
system to the new system, replaced system registry hive and NTOSKRNL,
checked the boot.ini then you'll be able to reboot the new system
without errors of consequence.
After the final reboot it is possible that NT will warn you about
certain services not being started. This has mostly to do with the
difference in hardware (network, video and scsi cards) between the
source and target system (and the system hive switch). To resolve any
device errors you will have to remove almost (stay away from the
registry LEGACY entries) all registry entries pointing tot the
non-existent hardware device/driver. For example you may have to do
this if network cards differ between machines:
- first, remove non existing cards thru the network panel,
- second, remove any network card registry entries detected during DR
partition install, this one dissappeared from the system
registry hive during the hive swap, but references to the
resource still exist in other parts of the registry,
- third re-instate the installed network card thru the network panel
Last but not least, as Kelly wisely suggested in an earlier mail, get
procedures in place to handle DR at the application level. Use a
hardware independant NT installation method, preferably one that will
also install (and configure) any and all necessary applications.
have to go,
regards Walter Ridderhof.
______________________________ Reply Separator _________________________________
Subject: Re: NT recovery Simulation
Author: Stephens AT storsol DOT com at INET-1
Date: 4/10/00 2:28 PM
Mehdi:
With the information you provided it looks like
the problem is with your boot.ini file.
You need to modify the Partition(2) variable to a (1) since you are now
booting from the c: drive.
John Stephens
Storage Solutions Specialists, Inc.
Tivoli Certified Consultant - ADSM V3
IBM Certified Specialist - AIX
http://WWW.Storsol.comWk: 813-265-3707
Fax: 520-441-9829
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
> Amini, Mehdi
> Sent: Monday, April 10, 2000 2:14 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: NT recovery Simulation
>
>
> I am trying to simulate a disaster recovery of one of our NT
> boxes. I have
> done the following:
>
> 1) Setup a hardware similar to the failed PC with 2
> partitions (C & D).
>
> 2) Partition 2 (D) will b used to recover partition 1 (C)
>
> 3) Installed WINNT on D along with Service Pack 6 and ADSM.
>
> 4) Retored Failed Server (NT Server, ADSM, ADSM.SYS...) onto C:
>
> 5) Copied BOOT.INI, NTLDR & NTDETECT.COM from original
> server on to the
> new PC.
>
> 6) Restarted PC.
>
> 7) Received error NTOSKRNL.EXE missing or corupted.
>
> What am I Missing here. and if anyone has done similar thing with success
> what have you done.
>
> Thanks
>
> Mehdi Amini
> Valueoptions
>
PLEASE NOTE:
The information contained in this electronic mail message is
privileged and confidential, and is intended only for use of the
addressee. If you are not the intended recipient, you are hereby
notified that any disclosure, reproduction, distribution or other
use of this communication is strictly prohibited.
If you have received this communication in error, please notify
the sender by reply transmission and delete the message without
copying or disclosing it.
|
