Hi,

There are a lot of fixes in the V5.2.X series of ITSM, and if you use this in a 
library client - manager config there are serious reasons to do upgrades. 
Please take a look at the patches fix in the different patch and maintenance 
releases. 

ftp://ftp.rz.uni-karlsruhe.de/pub/tsm/mirror/

I think if you get the list of fixed items from the latest maintenance release, 
you will have the ammo to convince your management to give you some downtime. 
Also, there is some issue's concerning db back-ups and crashing library 
managers mentioned in the 5.2.1.0 list of fixes.

Regards,

Karel


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Cain, Jason (Corporate)
Sent: dinsdag 27 juli 2004 17:09
To: ADSM-L AT VM.MARIST DOT EDU
Subject: 3494 library sharing serious problem - HELP!


Has anyone done this successfully at code level 5.2.0.1.  I have 2 TSM servers 
both at the same code level, I am trying to do library sharing using the TSM1 
server as the library manager and TSM2 server as the client.  The paths are 
defined to TSM1(the manager) and everything works except a DB backup.  I can 
dump disk pools on TSM2 to TSM1 and write backups directly to tape, however 
when I do a DB backup (backup db type=full devclass=3590tape) the client TSM2 
crashes.  TSM actually goes down and produces a core dump.  Per TSM support, 
there is a known bug(Internal Defect #11305), which is a enter process 
communication problem, and there is no documentation on it.  I just have to 
take TSM support's word.  As you all know, it is hard to convince management to 
take an outtage without some formal doc.  Per TSM support I have to upgrade to 
5.2.1.0 to resolve the issue.

OK....If there is a communication problem then why can I dump diskpools and 
write data directly to tape to the TSM library manager?

Any suggestions or comments would be great...

Thanks,
Jason