We use ADSM and will upgrade to TSM in the near future.  We have NT 4.0 on 
Compaq Proliant servers, RAID 5 arrays, ADSM clients and an ADSM server hooked 
up to a StorageTek silo. It works great for file system restores and is fast 
but isn't great as a server recovery tool.  What we have done to get rid of the 
time consuming NT and ADSM client re-installs when encountered with a server 
restore, is to do regular image backups of the C: drive to DAT tapes installed 
on the servers.  The backup software allows us to boot to these tapes and 
restore the image.  In one step you got your NT server and ADSM client 
configured and ready to go.  At this point ADSM comes in and restores the rest 
of the drives on the server.  Mind you, we currently only have a few clients so 
cost isn't that big of an issue when it comes to the DAT drives.  Might not be 
practical in a big shop with a whole lot of clients.  Believe me, we've tested 
NT server restore's using the same scenario you describe and have always had 
problems.  Too time consuming and you don't get everything back b/c ADSM can't 
backup open files.  We'll use the same strategy when migrating to TSM.  There 
is another way if you can't get DAT drives, but I wouldn't recommend that 
either.  Good luck!


>>> Shekhar.Dhotre.B AT BAYER DOT COM 07/26 2:38 PM >>>
        Any advice on the following NT server restore scenario would be
greatly appreciated.

        Objective:  Restore an NT server.

        Test scenario:
            Complete TSM3.7.2  running on H-70 (AIX 4.3.3)backup of NT server
including registry.
            remove all data from server
            install windows NT Server operating system
            logon to NT server
            install TSM3.7.2 client code
            Modify TSM3.7.2 options file
            Start TSM3.7.2
            RESTORE ENTIRE C DRIVE (on which the NT system resides)
            RESTORE Registry

        Results:
            TSM3.7.2  restores 1000's of files.
            88 files not restored adsm access denied (in use by NT?).
            system rebooted
            system not functional

        Players:
            Windows NT 4.0 "compaq proliant , with RAID5 array,  " Nt experts ,
and me

        My opinion:
                Should you expect to restore the operating system over
                itself, have 88 failures and expect to obtain a bootable
                system??? I would think not!
        Their opinion:
                This has to work since trying to determine what system files
                should be restored or not restored is tooooooo difficult.
                TSM3.7.2 is a failure!

        Thanks for any input. (violence is not an option)

             shekhar Dhotre , Bayer Diagnostics , 508-359-3872