Here's an example of an aix restore (of incrementally backed up data) from =
one box to another box.=20

>From sourcenode1, grant access to sourcenode1's backup data to targetnode2:=

       dsmc
        tsm> set access backup * targetnode2  *
        tsm> q access

If you want to increase sessions/tape drives for the restore:
         Change maxmountpoints for targetnode2 to however many tape drives =
you can afford (update node command)
         Add  resour #  to targetnode2's dsm.sys file (where # is one more =
than maxmountpoints)=20

>From targetnode2:
         # dsmc
          tsm> q ba -fromnode=3Dsourcenode1 /directory-to-restore =
-pitdate=3Dmm/dd/yyyyy -pittime=3Dhh:mm:ss -subdir=3Dyes  (use the query =
to ensure you have the restore syntax correct)
         nohup dsmc restore -fromnode=3Dsourcenode1 "/directory-to-restore/=
" /new-directory-name/ -pitdate=3Dmm/dd/yyyyy -pittime=3Dhh:mm:ss  =
-subdir=3Dyes > /tmp/tsm/logs/restore-fromnode1.log &

Be sure to change back the maxmountpoints and remove the resour # from the =
dsm.sys.

Also, review the "preservepath" option if you are concerned with the =
directory structure that you're restoring:

           dsmc
            help
           117

1c.lxxx)  Preservepath

      The preservepath option specifies how much of the source path to
      reproduce as part of the target directory path when you restore or
      retrieve files to a new location. Use the -subdir=3Dyes option to
      include the entire subtree of the source directory (directories
      and files below the lowest-level source directory) as source to be
      restored. If a required target directory does not exist, it is
      created. If a target file has the same name as a source file, it
      is overwritten. Use the -replace=3Dprompt option to have Storage
      Manager prompt you before files are overwritten.