I think you are going to have to go with option 1 if you want to transfer
the db (not export/replicatie data) because you can't restore a 6.1 TSM
database on a TSM 6.3 software stack.
This did work with TSM 5 where you could run an upgrade db command after
the restore, this is no longer an option with TSM v6 I think.

I didn't check this so I might get corrected here. :-)


On Wed, May 22, 2013 at 4:53 PM, white jeff <jeff.white3 AT blueyonder.co DOT 
uk>wrote:

> Hi
>
> TSM Server v6.1.5.0
> On Windows 2008
>
> I have a need to upgrade TSM to  v6.3.3
>
> On the same physical host, no problem, straight forward
>
> The current host is 32-bit, so we will move TSM onto a new physical host
> with more memory and of course it will be 64-bit to support TSM v6.3. Can't
> get away from this as the customer has already purchased the hardware.
>
> My question: IBM have a documented migration path from v5 to v6, running on
> a different physical host. There is also the v6-v6 upgrade path on the same
> host. Have performed both without issues.
>
> But are there any special requirements for v6-v6 across different hosts?
>
> I was thinking either:
>
> 1) Install v6.1 on the new host, then upgrade to v6.3
> or
> 2) Build v6.3 on the new host, then restore a v6.1 database backup down
> onto v6.3, if that is possible. I remember doing something similar in v5,
> where the DR server was a higher v5 than the production server. TSM warned
> me when i restored the database, but was happy to run the restore.
>
> I guess the the other thing to consider is moving the library connectivity
> from the old to the new host.
>
> Comments/Thoughts welcome
>