Martha,

If the tape is in a stgpool on the target server, that's a GOOD thing.  With
the later versio TSM servers, a server-to server export can be done directly
in 1 step.  The exported data lands in whatever pool is specified by the
appropriate mgmt class/copy group on the target server, and you're done,
you don't have to do the import step.

On the target server, do a q filespace - the data for your exported client
should be where it belongs.  Test a restore to be sure (if you have a client
it can be restored to!)

Wanda

er export, the data lands in the pool according

On Tue, Jul 8, 2008 at 2:09 PM, Martha McConaghy <URMM AT vm.marist DOT edu> 
wrote:

> We are moving to a new TSM server on a Pseries box with an IBM 3592 tape
> system from a very old mainframe based TSM server.  We had not planned on
> moving any of the old data over to the new server as there was no
> requirement
> for it.  However, we run into a single user who wants to have all of his
> previous backups moved to the new server, even though most are no longer
> usable (we are talking about old OS2 systems, etc....every PC he has ever
> used in the last 20 years).  Since this user is our 2nd line manager, we
> have
> no choice to try and figure something out.
>
> The main problem is that the two servers are not compatible.  The old
> server
> can only talk to 3590 tape drives, whose tapes are not usable in the new
> 3592s.  So, I can't just export the data to tape and then import into the
> new server. (Ah if only life were that easy!).
>
> On a hunch, I've tried creating a server connection between old and new
> TSM server.  Then, I exported a filespace to a virtual volume
> (devclass=server) on the new server.  It sits on a 3592 tape right now.
> However, the new server will not allow me to import this tape, as it
> belongs
> to a pool and it thinks it is in use.
>
> Is there any way to make this work?  I'm at a loss for ideas at this point.
> I could create a virtual volume on disk and move the old filespaces to it,
> but then I'll have to keep the old server running "forever" or at least
> until
> it will run no longer.
>
> Anyone have any ideas?
>
> Martha McConaghy
> Strategic Planner/Project Manager
> Marist College IT
>