I am a little confused by this.  The procedure I tested - and is in
     the RedBook - uses a "repair partition" for a small NT system with an
     ADSM client to restore the NT system to its primary partition.  This
     way the functioning OS is not trying to camp restored files on top of
     itself.  After the partition restore, the registry files need to be
     copied from ADSM.SYS to the system directory and this can be done with
     NT Explorer because they are just plain files to the repair partition
     system.

     Other than a few glitches with the boot.ini files due to my creation
     of the repair partition after the backup (and the disk corruption)
     this worked like a charm.

     Is the following intended for an ADSM client or and ADSM server?

     Why no repair partition?  hmmm.

     eric.lewis AT doit.wisc DOT edu


______________________________ Reply Separator _________________________________
Subject: IBM and Data Recovery
Author:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>  at IPNET
Date:    9/15/98 1:43 PM


This is IBM's new recovery based on their brs home page. Has anyone used
this method with ADSM and can you tell us how well it works.  I am looking
at testing  this this week and was looking for insight.
Server Recovery Procedure
1.      Install, configure, and connect the target server hardware
2.      Install Windows NT Server 4.0 on the target server, if additional
disk subsystem adapters need to be specified follow the prompts for adding
the additional adapters as necessary then continue
3.      Install the SAME service pack level on the target server as the
source server
4.      Install the tape backup/restore software and any tape backup/restore
software service packs that were applied to the source system on the target
system
5.      Restore all drive partitions to the target server from the source
server tape EXCLUDING the following files. BOOT.INI, HAL.DLL, and
NTOSKRNL.EXE
6.      Shutdown the system and restart the system
7.      Place the Windows NT Setup #1 disk in the floppy drive A: and follow
the setup process. If additional disk subsystem adapters need to be
specified follow the prompts for adding the additional adapters as necessary
then continue until you get to the LICENSE agreement.
8.      Follow the instructions specified within the LICENSE agreement.
9.      Press "ENTER" to accept the option to upgrade WINDOWS if you DO NOT
HAVE THIS OPTION once the license is agreed to you will have to reboot and
go back to POINT ONE. Note: This may happen if all the necessary disk
subsystem adapters/device were not detected
10.     Follow the upgrade option by pressing "ENTER" to continue with disk
examination. This has a TEXT based section which will prompt you to reboot.
Follow the on-screen instructions to continue to restart the system and take
you to a GUI based section of the setup
11.     Follow the on-screen instructions to continue and accept the
defaults as you proceed. If prompted to install Microsoft Internet
Information Server, deselect this option and continue. At the end of the GUI
based section of the UPGRADE process restart the system as instructed
12.     If prompted about the display resolution select "OK" and test the
video as instructed to continue
13.     Windows NT should now be working, however the integrity of the
network and system configuration must be re-verified. Remove any unnecessary
drivers associated with the hardware of the source system via the "Control
Panel" (ex. disk subsystem adapter drivers). Note: Use the system "Event
Log" to aid in determining which drivers are acceptable to remove. Using the
"Network Control Panel" applet, remove/add/reconfigure the network
adapter(s). Information such as the TCP/IP address information will be
needed here if applicable
14.     Shutdown and restart the system
15.     At this time, re-apply the applicable Windows NT operating system
service pack.
16.     Restart the system after the service pack has been applied
17.     Verify the integrity of the DOMAIN and SHARES by using the normal
Windows NT administration tools (ex. Server Manager and User Manager For
Domains) Note: If the server being restored is resides in a resource domain,
trust relationships will need to be reestablished with the appropriate
accounts domain
18.     The restore of the server is now complete

David Beardsley
Sr. Technical Programmer
Winn Dixie Stores Inc.
WWW.WINNDIXIE.COM <http://WWW.WINNDIXIE.Com>
"Good judgment comes from experience, and a lot of that comes from bad
judgment."