You can't copy just some DB entries.
Other people have reported success with restoring the TSM DB to the new
server, then deleting the unwanted filespaces/nodes on the new server.

But you need to review your tape inventory carefully.  The fact that your
storage pool is collocated doesn't mean that tapes necessarily have data for
only one client.  If there was ever a day where you ran short of scratch
tapes, TSM would have started stacking multiple clients per tape.

 I'd recommend checking each tape before moving it would be a good plan.  If
there are multiple nodes on a tape, you can use MOVE DATA to force the data
to other volumes in the storage pool; if scratch tapes are available,
collocation will be honored on output.  I think that would be less trouble
than cleaning up the mess after a move.



On Thu, Nov 20, 2008 at 9:32 AM, Henrik Ahlgren <pablo AT elma DOT net> wrote:

> Hi,
>
> I have a simple question.
>
> Let's say that I'm splitting a large TSM server instances into few smaller
> servers, using a shared library with library manager/client architecture.
>
> Now, if there are pretty big client nodes whose data is on collocated
> tapes, can I move a node between servers without copying the data to new
> tapes with export? Since collocated tapes have only data from one node, it
> should be possible to copy just the DB entries and change the ownership of
> the volumes in the library manager. Is there a way to do it?  Or any other
> good ideas on how to migrate nodes between TSM instances without using too
> much tape media/network bandwidth/time/effort?
>
> --
> Terveisin
>
> Henrik Ahlgren
> Technical Manager
> Itella Information Oy
>
> Tietäjäntie 2
> FI-02130 Espoo
> GSM +358-50-3866200