Thomas,

Cannot speak about NT restores specifically, but have had some experience of
Novell restores and do not see why from a TSM view they should be different.
Say you want to restore client A's filespaces to client B
With Netware you just specify the nodename of client A in the dsm.opt of client
B
Then you kick of a command line restore from client B something along the lines
of
load dsmc rest  -tapep=n -repl=n -su=y A\data:\   B\data:\
You have told TSM that for the purposes of the restore Client B is client A, so
it will restore
client A's data to the tcpip address that you have initiated the restore from.
We actually use a separate "contingency" client for this type of disaster
recovery restores,
but if you do not then you need to ensure that after the restore you change the
nodename in
client B back to its real name, and of course that old caveat  with Novell of
relading the client scheduler to pick up the dsm.opt change. With NT I believe
the same is achieved by stop/starting the scheduller service.

Hope this helps,
John


**********************************************************************
The information in this E-Mail is confidential and may be legally
privileged. It may not represent the views of Scottish and Southern
Energy plc.
It is intended solely for the addressees. Access to this E-Mail by
anyone else is unauthorised. If you are not the intended recipient,
any disclosure, copying, distribution or any action taken or omitted
to be taken in reliance on it, is prohibited and may be unlawful.
Any unauthorised recipient should advise the sender immediately of
the error in transmission.

Scottish Hydro-Electric and Southern Electric are trading names of
Scottish and Southern Energy Group.
**********************************************************************