Don't try to restore the NT.  Just restore the data.

Your DR plan for an NT machine with a couple of applications might look
something like this:

Install NT
Install SP6
Configure IP as follows: blah, blah, blah.
Install SQL Server (from the CD)
Install Application XYZ (from the CD):
Installation instructions for XYZ: blah, blah, blah.
Install the *SM client software as follows: blah, blah, blah.
Restore the data from *SM using the following commands:

restore d:\XYZ\data\* -subdir=yes replace=all

(This restore might even be to a completely different place)

Bottom line: make the restore application specific not machine specific.
You can't do otherwise for real.  Consider an outfit that has 100 NT
servers.  Are they going to have 100 NT servers at the DR Site?  Are they
going to re-create these 100 NT Servers during a real disaster?  No way.

I don't think one should ever plan on restoring the OS (perhaps on any
platform) during a disaster.  I believe all DR plans should be written based
on restoring applications and application data.  This restoration should be
as machine independent as possible.

If you begin to view this as a strength rather than a weakness you will have
tons more flexibility during a real disaster.  It requires a bit more
planning: you can't just presume to restore the C drive and all other drives
and everything will be lovely (but as you pointed out, you can't do that
anyway!).  You have to have a better plan.

Kelly J. Lipp
Storage Solutions Specialists, Inc.
PO Box 51313
Colorado Springs CO 80919
(719)531-5926
Fax: (719)260-5991
www.storsol.com
lipp AT storsol DOT com