Yep, assuming your target TSM server has a compatible drive.

EXPORT NODE blah  "look up the applicable parameters" devclass=tapedevclass

Will take the .9 TB of data backed up to TSM and put it in a portable format
on n tapes.
You then enter an IMPORT NODE command to load it into the DB and storage
pools of your target server.

How long that takes on the target server depends on how many objects have to
be created, the speed of the drives and storage pool media, etc.  And then
you've still got to do the RESTORE to your target server, one filesystem at
a time.  So the practicality sort of depends on what "too long" means...





On 2/7/08, Larry Clark <lclark01 AT nycap.rr DOT com> wrote:
>
> Currently I am migrating servers for a customer. In all instances but one
> I
> am using a combination of mksysb and sysback on uservgs to do this.
>
> One node has .9TB of data, however and would take too long using sysback.
>
> Someone has suggested using TSM. Can the client node be exported to tape
> and
> imported on a TSM server at the target site?
>