Dan,
I think, that it is not necessary to install an interim NT version on an
additional partition. Just install any NT with any options on the
primary boot partition (C:).
When restoring all files over the interim install, all options are
overwritten, the registry-restore replaces the old one as soon as you
reboot the system.
Note that it is not necessary to install the same service-pack level, as
the kernel gets replaced, too.
The procedure is for disaster recovery, but not intended for a change in
hardware. By recovering the registry, you bring back the complete system
configuration that is definitly hardware-dependent. So get sure that you
recover on the SAME or IDENTICAL machine when recovering the full
registry.
Another comment to Julie's recovery method:
By restoring to a FAT partition all of the files' security information
gets lost. It's much better to restore to a NTFS partition.
Regards
Michael
--
Michael H. Bartl, ADAC e.V. (IDL/PPO)
Michael H. Bartl, ADAC e.V. (IDL/PPO)
Tel.: (089) 7676-4063, Fax: (089) 7676-8161
EMail: Michael.Bartl AT Zentrale.ADAC DOT de
>----------
>Von: dan thompson[SMTP:thompsod AT USAA DOT COM]
>Gesendet: Freitag, 4. Juli 1997 06:13
>An: ADSM-L AT VM.MARIST DOT EDU
>Betreff: Re: Win NT disaster recovery
>
>Michael,
>
> As I understood the question the scenario is that a interim install of NT
>is being used to facilitate the restore of the original system/boot
>partition to another partition. If this is the case, the REGREST falls
>short because it only updates the registry of the currently active boot
>partition. This is why I pointed out the alternative of using ADSM to
>restore files in the adsm.sys directory.
>
>However, then apparent intent of your reply raises an interesting question.
> Is it really necessary to have an interim install of NT?
>
>Do you or other forum participants see a fault with these steps to restore
>a NT server to a machine of a significantly different config.?
>
>1) Install NT and ADSM on the destination machine. Make certain that NT is
>in
> the same location on this machine as on the original (and same
>version/build).
>
>2) Restore the files/directories for the logical drive NT runs from.
>
>3) Restore the registry entries except for SYSTEM using REGREST.
>
>4) Power down or shutdown clean. (I am assuming that a clean shutdown will
>not
> not corrupt the registry under this scenario)
>
>5) Complete restoration of all other logical drives.
>
>I have two concerns I would to have other opinions on. It seems to me the
>SYSTEM hive has a significant amount of data that will not be restored. A
>prime example is the service information which is under the
>current_control_set keys.
>
>The other concern is that NT has special handling when the hardware used
>has SCSI drives that are not supported by that machines BIOS. When this
>situation exists the driver file for those hard drives is copied to the
>root directory of the system partition.
>NT renames this file. If there is a discrepancy between the original or
>destination machines pertaining to these types of drives, there will have
>to be special consideration during the LAN server recovery.
>
>
>
>----------
>> From: Bartl, Michael <michael.bartl AT ZENTRALE.ADAC DOT DE>
>> To: ADSM-L AT VM.MARIST DOT EDU
>> Subject: AW: Win NT disaster recovery
>> Date: Thursday, July 03, 1997 10:44 AM
>>
>> Julie,
>> to restore the registry there's no need to restore the adsm.sys
>> directory, because there's an extra command in both GUI and CL-client.
>> You'll find the REGREST command in 7.5.16 of ADSM's manual for the
>> NT-Client.
>> Let me just quote a short passage of this page:
>>
>> ##################################
>> 7.5.16 DSMC REGREST--Restoring the NT Registry
>>
>> Use the REGREST command to restore the NT registry.
>>
>> This command is not valid for the Windows 95 client.
>>
>> When registry keys are restored, a backup copy of the active registry
>> keys is made in the ADSM.SYS\Registry.Sav directory on the system
>> drive's root directory (usually called WINNT or WINNT35) before the
>> registry is restored.
>>
>> When you restore a registry key, ADSM asks you if you want to activate
>> the restored key. If you say yes, you must reboot the machine in
>> order to activate the restored registry.
>>
>>
>> Syntax
>>
>> +-----------------------------------------------------------------------
>> -+
>> ¦
>> ¦
>> ¦ >>--DSMC REGREST---- ENTIRE-----------------------------------------><
>> ¦
>> ¦ +- MACHINE--- SAM---------¦ ¦ <--------+ ¦
>> ¦
>> ¦ ¦ +- SECURITY-¦ ¦ +--- options---+
>> ¦
>> ¦ ¦ +- SOFTWARE-¦ ¦
>> ¦
>> ¦ ¦ +- SYSTEM---+ ¦
>> ¦
>> ¦ +- USER--- DEFAULT--------+
>> ¦
>> ¦ +- CURUSER-+
>> ¦
>> ¦
>> ¦
>> +-----------------------------------------------------------------------
>> -+
>>
>> ############################
>> I think SEAGATE uses the same method in BackupExec and this is how they
>> explain the feature in the manual:
>> NT has a built in feature to schedule the copy process of any open files
>> to the next system restart. There's a switch in NT's registry that
>> enables the process, so BackupExec creates a set of files that should
>> overwrite registry and other critical files like the Kernel itself and
>> you simply restart the system to get the changes alive.
>>
>> Regards
>> Michael
>> --
>> Michael H. Bartl, ADAC e.V. (IDL/PPO)
>> Tel.: (089) 7676-4063, Fax: (089) 7676-8161
>> EMail: Michael.Bartl AT Zentrale.ADAC DOT de
>> >
>
|
