Julie,
Congratulations!!! It is my opinion that your success is pretty
impressive considering that the design of NT has done almost everthing
possible to make success impossible.
I have one question. In your final step, you state that you "booted from
c: partition".
Prior to doing this did you modify the boot.ini file to point to the NT
files on drive c: instead of drive d:? If not, you loaded NT from the D:
drive and not the C: drive. Please don't mail me any ticking packages if
this is true.
I think that the difference in HAL.DLL should be investigated a little
further by someone. HAL, as you probably already know, stands for Hardware
Abstraction Layer. There being a discrepancy in a DLL file is unusual if
NT is the same version/build. I can only think of
a few possible causes of this.
a) OEM versions of NT being used.
b) HAL.DLL being modified by a fixpack.
c) NT install copies over different versions of HAL.DLL depending on
machine type.
d) Some processing by NT that builds unique versions of HAL.DLL for each
config. I
doubt that such a mutant process exists.
It seems much easier to use your methodology of just copying the file from
the new build. However, I am little uneasy about what else is different.
Good Luck,
Dan T.
----------
> From: Julie Phinney <julphinn AT EMPHESYS.E-MAIL DOT COM>
> From: Julie Phinney <julphinn AT EMPHESYS.E-MAIL DOT COM>
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: NT disaster recovery
> Date: Friday, July 04, 1997 1:54 PM
>
> Hi all -
> THANKS for all the suggestions on restoring NT to unlike hardware.
> After 16 fruitless (well, seemed fruitless anyway) hours yesterday, it
> came together in 1 hour today. Here's what I had to do:
> 1. Format the C: partition FAT and leave it empty
> 2. Install the D: partition FAT and install NT and ADSM on it.
> I used the same machine name and domain name as the original machine
> 3. Do a DSMC RES {SYS}\* -SU=YES -REP=ALL
> SYS is the drive label of the C: drive on both the original machine
> and the new machine
> 4. Do an ATTRIB BOOT.INI -S -H on both C:,D: and copy D:\BOOT.INI C:\
> 5. Copy D:\WINNT\SYSTEM32\HAL.DLL C:\WINNT\SYSTEM32
> (This fixed an error about invalid HAL.DLL on bootup after restore)
> 6. Copy C:\ADSM.SYS\REGISTRY\id\MACHINE\*.* C:\WINNT\SYSTEM32\CONFIG
> Copy C:\ADSM.SYS\REGISTRY\id\USERS\*.* C:\WINNT\SYSTEM32\CONFIG
> where id is the machine name of the source machine. This skips a
> subdir under USERS called SYSTEM. It has 2 files, SYSTE000 and
> SYSTE000.KEY that I didn't copy over, and don't know what they are
> 7. Delete C:\WINNT\SYSTEM32\CONFIG\SYSTEM
> 8. Boot to DOS and copy D:\WINNT\SYSTEM32\CONFIG\SYSTEM to C:\same
> 9. Boot up the new C: partition.
> That's it. It seems to boot up fine now. I don't know if it has full
> functionality of the original. I'll ask someone to help test when the
> holiday is over. If I run into any changes to the above plan, I'll
> let you all know.
> I guess I would summarize the above plan as
> 1. Create 2 partitions, install NT on 1 of them, format them FAT.
> 2. Restore to the blank one.
> 3. Copy the restored registry that sits in ADSM.SYS to the proper
> location. Then delete the SYSTEM hive and copy it from your other
> partition. Copy HAL.DLL and BOOT.INI from your other partition as
> well.
> My 2 machines are significantly different, one being an HP Netserver
> with RAID and the target being an HP Vectra, no raid or special
> devices.
> Thanks again.
> Julie Phinney
> JULPHINN @ EMPHESYS.E-MAIL.COM
|
