You might look at new features introduced with TSM 6.3, for server/node 
replication.

At 10:47 AM 11/16/2011, Dury, John C. wrote:
>Our current environment looks like this:
>We have a production TSM server that all of our clients backup to throughout 
>the day. This server has 2 SL500 tape libraries attached via fiber. One is 
>local and the other at a remote site which is connected by dark fiber. The 
>backup data is sent to the remote SL500 library several times a day in an 
>effort to keep them in sync.  The strategy is to bring up the TSM DR server at 
>the remote site and have it do backups and recovers from the SL500 at that 
>site in case of a DR scenario.
>
>I've done a lot of reading in the past and some just recently on the possible 
>ways to migrate from an AIX TSM server to a Linux TSM server. I understand 
>that in earlier versions (we are currently at 5.5.5.2) of the TSM server it 
>allowed you to backup the DB on one platform (AIX for instance) and restore on 
>another platform (Linux for instance) and if you were keeping the same 
>library, it would just work but apparently that was removed by IBM in the TSM 
>server code to presumably prevent customers from moving to less expensive 
>hardware. (Gee, thanks IBM! <sigh>).
>I posted several years ago about any possible ways to migrate the TSM Server 
>from AIX to Linux.
>The feasible solutions were as follows:
>
>1.       Build new linux server with access to same tape library and then 
>export nodes from one server to the other and then change each node as it's 
>exported, to backup to the new TSM Server instead.  Then the old data in the 
>old server can be purged. A lengthy and time consuming process depending on 
>the amount of data in your tape library.
>
>2.       Build a new TSM linux server and point all TSM clients to it but keep 
>the old TSM server around in case of restores for a specified period of time 
>until it can be removed.
>
>There may have been more options but those seemed the most reasonable given 
>our environment. Our biggest problem with scenario 1 above is exporting the 
>data that lives on the remote SL500 tape library would take much longer as the 
>connection to that tape library is slower than the local library.  I can 
>probably get some of our SLAs adjusted to not have to export all data and only 
>the active data but that remains to be seen.
>
>My question. Has any of this changed with v6 TSM or has anyone come up with a 
>way to do this in a less painful and time consuming way? Hacking the DB so the 
>other platform code doesn't block restoring an AIX TSM DB on a Linux box? 
>Anything?
>
>Thanks again and sorry to revisit all of this again. Just hoping something has 
>changed in the last few years.
>John


--
Paul Zarnowski                            Ph: 607-255-4757
Manager, Storage Services                 Fx: 607-255-8521
719 Rhodes Hall, Ithaca, NY 14853-3801    Em: psz1 AT cornell DOT edu