>In <31A0D4AF3516D0118C810001FA442FC9692C0D@ARES>, on 02/04/98 at
>01:13
>PM,
>   Michael Bartl <michael.bartl AT ZENTRALE.ADAC DOT DE> said:

>>Not being able to provide identical hardware after a disaster case
>is
>>an unsolved problem we have, too.
>>I think we do not need the possibility of merging registry databases
>>or doing other tricks, as this all may lead to inconsistent system
>>configurations.

>>What we really need is a possibility to mark certain settings in the
>>registry as "changed" or "invalid" in a way that makes Windows NT
>>install the new components from the CDROM during next bootup.
><snip>
>I have found that their is NEVER a need to do a "Disaster Recovery"
>of
>an NT Server, ever (well, barring a disaster wiping out ALL the
>servers in a domain, that is).
><snip>

>This means, of course, that you should have a separate system
>partition (C) with only "re-installable" software on it.  All data
>should live on the DATA drive (which is backed up by ADSM). <snip>
>It does mean, however, that you need to have "installation media"
>handy for recovery (the NT CD, SQL Server CD, SNA Server, etc) and
>know how to do an initial install of all the software on the server.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Keith Medcalf       (416) 410-5791       http://www.dessus.com/ IBM
OS/2, LAN Server, DB2, TCP/IP, DOS, Windows 95,  Windows NT
 Finger or email kmedcalf-pgp AT dessus DOT com for my PGP Public Key