Avoid altering your TSM node identity with by planting a foreign
NODename value in the prevailing dsm.opt file: that can lead to
problems, particularly as TSM functions might be used by others on
that system while the change is in place.  Instead, use the
VIRTUALNodename option, which is intended for cross-node work,
specified on the command line.  See the client manual for info on
cross-node restorals ("Restoring or retrieving files from another
client node").

Specify the restoral as:
  Restore e:\* f: -subdir=yes -tapeprompt=no -quiet -
virtualnodename=whatever

I always recommend that rather than launching right into the restoral
attempt that a Query Backup first be done using the same general
specifications, to verify overall correctness, as in:

   dsmc query backup e:\* -subdir=yes -virtualnodename=whatever

If you encounter the ANS1084E, do
   dsmc query filespace virtualnodename=whatever
to verify the filespace identity.

   Richard Sims   http://people.bu.edu/rbs/