Since we use servers which accommodate hot pluggable drives we add an
"emergency disk" into our storage enclosures (or a bay in the server)
and boot with an NT emergency boot diskette in which the boot.ini file
points to the new disks partition. The emergency boot diskette has
NTKRNL NTLDR and boot.ini MS has procudures for building them (basically
format under NT and add the req files). The Emergency DISK has NT loaded
on a partition on it that can be referenced by the boot.ini file. We
also have ADSM installed on it. It is a simple matter to change the node
name and begin the disaster recovery scenario. So far it has worked
every time. I'm not sure that MS has plans to provide a method to bring
up a working NT system entirely from diskette, haven't heard of one
anyway.......
-Bob
James C. Harrer, SE/CRM, /Long Grove, G-5 JHARRER - CPOLNM01 wrote:
James C. Harrer, SE/CRM, /Long Grove, G-5 JHARRER - CPOLNM01 wrote:

> ===============================================================================
>
> RE:  Using ADSM to restore a Win/NT 4.0 Server operating system
>
> I heard many of you are successfully restoring Win/NT 4.0 OS using a
> separate
> bootable partition and then restoring to the real production boot
> partition.
> That sounds pretty good but leaves me with a question and a wish.
>
> 1.  What files, if any are excluded from backup?  I'm not sure the
> recommended
> include/exclude list that comes with ADSM is appropriate.
>
> 2.  I do not like having to install a second bootable partition on all
> my
> Win/NT systems.  It wastes space and complicates startup procedures
> for my
> customers.  Is there any hope of getting a procedure to boot a down
> machine
> from diskettes, do a virtual drive attachment from a different Win/NT
> systems
> and restoring the down operating system partition from there?