Mike,
it is a good idea to install a second NT to a directory different from the
(lost) productive one. You start this NT, copy boot.ini asied (not needed,
but helpful in case of failure) install ADSM and restore all the stuff from
ADSM. This restore should bring back everything since you have no open
files in the NT directory that ADSM wants to overwrite. It may be required
to put back the registry files from the adsm.sys-directory to the new
NT-directory (where they belong: %WinNTRoot%\system32\config\).

Having done this, everything should work fine again. But you should be
aware of problems with WinNT domain structure. It is recommended not to put
the emergency-NT into a domain structure but to put it into a NT-workgroup.

Yours,
Matthias






Mike Dillon <Mike.dillon AT WCOM DOT COM> am 19.10.99 18:13:39

Bitte antworten an "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


An:   ADSM-L AT VM.MARIST DOT EDU
Kopie:     (Blindkopie: Matthias Hensel/BE/USR/SHG)


Thema:    Need Help





Does anyone have information about using NT Clients being backed-up by a
Unix ADSM server.  We have experienced successful restores of the NT
server OS's, however when we try to restore the applications they fail.
Errors are received and the applications are lost.  Scenario:  NT 4.0
with IIS 4.0, several virtual sites setup and when a backup is complete,
we format the server and install OS and ADSM backup client.  Once the
client is installed the  we begin the restore.  Aproximently 115 files
are not restored, many in the winnt\system32 directory.  The IIS is not
restored.  Does anyone have any experience trying to restore
applications from a ADSM server to the NT clients?


Michael Dillon
Sr. NT System Administrator