Why you don't install a new instance of adsm (c:\winnt.tmp\adsm.tmp) on =
the
crash'd node=20
and restore direct from that node.=20
Copy registry should also be possible. Only boot.ini must be modified.
Regards,
Stefan Holzwarth

> -----Urspr=FCngliche Nachricht-----
> Von: Loon, E.J. van - SPLXM [mailto:Eric-van.Loon AT KLM DOT NL]
> Gesendet am: Mittwoch, 29. November 2000 13:02
> An: ADSM-L AT VM.MARIST DOT EDU
> Betreff: Re: NT Backup/recovery
>=20
> Hi Eric!
> Assuming your hardware is identical to the one before the=20
> crash, ours works
> like this:
> We are using a dedicated client (lets call it node A for now)=20
> through which
> recovery is done.
> 1) Allow on all your managed NT machines access to the backup=20
> data for node
> A. Use the User Access List option to do this.
> 2) Install NT on the crashed server in a temporary directory, e.g.
> c:\winnt.tmp. Create a generic administrative account on this=20
> machine and
> again add node A to the User Access List.
> 3) Start TSM on node A and use the Access Another User option=20
> to access the
> crashed nodes backup data.
> 4) Start a restore of this data and select the complete C=20
> drive for the
> restore. Select the option "restore to original location" in=20
> the restore
> panel. Node A will now restore the data directly to the=20
> crashed node (it
> uses the administrative share \\machinename\c$ to do this).
> 5) After the restore, log on to the crashed node, copy all=20
> the registry
> files from c:\adsm.sys to c:\winnt\system32\config and change=20
> the Windows
> directory from \WINNT.TMP to \WINNT in the c:\boot.ini and reboot the
> crashed node.
> 6) As soon as it's up and running you can delete the=20
> C:\WINNT.TMP directory.
> That's it!
> There is a Microsoft article on how to restore NT to=20
> different hardware
> (http://support.microsoft.com/support/kb/articles/q139/8/22.as
p) but we
haven't tested it yet.
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines