This is a case of Pick your Poison;

a) start clean on Windows, let the initial backup take 10 days while you 
continue to get backups on your Linux box
b) start clean on Windows, move the data with incremental import/export while 
you continue to get current backups on your Linux box
c) upgrade to V6.3  on both sides, let TSM replicate from Linux to Windows 
while you continue to get current backups on your Linux box

Depends on why that "initial" backup takes 10 days; if it's the usual slowness 
associated with pulling NAS data across CIFS, option b) might be the fastest. 

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Allen S. Rout
Sent: Monday, August 13, 2012 8:42 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] DB from Linux to Windows

On 08/12/2012 10:04 PM, Steve Harris wrote:

> I have a situation where the design that was originally implemented to 
> back up some NAS Filers using a Linux TSM Server has not worked out in 
> practice. We are thus looking to re-implement on Windows. I'd really 
> prefer not to have to do everything from scratch particularly as the 
> initial backup takes on the order of 10 days.

Is there some aspect, other than the platform itself, which suggests that a 
Windows TSM server will answer this need better than a Linux one?


> Has anyone tried to restore a TSM V6 DB from Linux to windows? If its 
> not directly possible can it be "converted" using DB2 export/import 
> tools?

The canon is that you can't restore cross-platform, which I guess you
know.   I think that if you used DB2 level tools to shoehorn a backup
from platform A into platform B, you'd be in an Unsupported
Configuration par excellence.   I'd be afraid that it would mostly work,
as in not show problems for "A while", and then leave you up a semiliquid creek.



- Allen S. Rout