When we were upgrading our large 11 year old DBs from 5.4 to 6.2, we used a 6.2 
library manager for about a month with no issues.

As a side curiosity question, how big is too large, my biggest 5.4 was a little 
of 250GB and our two 11 year old DBs were over 200GB.  No issues upgrading.

Andy Huebner


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Steven Harris
Sent: Wednesday, October 09, 2013 7:04 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Library Manager/Client compatibility problem

Hi all

I've painted myself into a corner.

I have a customer with TSM V5.5.6 and V6.2.4 instances hosted on AIX.

The original plan was to move the clients one at a time off V5 and onto v6.
 The V5 database is too big to convert, and as the instance is over 10 years 
old I fully expect it to have database issues that may make a conversion 
difficult.

The customer sees this as essentially wasted work and wants me to implement TSM 
for VE as quickly as possible since most of those V5 clients are (now) 
virtualized Windows and Linux boxes.

There are dual sites with TS3500s and TSS1120/1140 drives, with a library
manager on each.   I'd be mad to install anything other than TSM for VE at
6.4, so I'll need the TSM for VE instance to be 6.3.4.  This forces the library 
manager to also be 6.3.4, but library manager/library client is only supported 
at n+1, so the V5 library client is not supported with the
6.3.4 library manager.

It really would be a better option to go straight to TSM for VE if that can be 
done.

Is anyone out there successfully running V5 lib client against V6.3 lib 
manager?  Anyone got horror stories to tell?

Thanks

Steve

Steven Harris
TSM Admin
Canberra Australia