There is known problem when upgrading from 3.x to 4.1 and you must use
"CONVERT ARCHIVE <node_name> REORG=Yes" for each node. The other approach
is to start at least once the GUI client (usualy you do not backup the
server manually but through command line client, right). This was included
in 4.1.2 or 4.1.3 and all later versions but if you are forced to stay at
4.1.1 you have to perform conversion by yourself.
Cannot prove is this the problem resolution but if it does not help also
does not harm. So give it a shot.

Zlatko Krastev
IT Consultant





"Rupp Thomas (Illwerke)" <thomas.rupp AT ILLWERKE DOT AT> on 15.01.2002 20:46:23
Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To:     ADSM-L AT VM.MARIST DOT EDU
cc:

Subject:        Bad performance after upgrading from 3.7.2.0 to 4.1.1.0

Hi TSM-ers,

we upgraded a few days ago from TSM 3.7.2.0 to 4.1.1.0. This upgrade was
done by our
IBM CE (it's a NSM with an 3494 ATL).
After the upgrade the performance dropped dramatically. I think it's a
problem with the
database because the cache hit rate dropped below 95% - it was in the 99%
area before.
Nothing else was changed. Only AIX was upgraded to 4.3.3 and TSM was
brought
to 4.1.1.0.

Are there any recommendations what settings I should change to bring
performance back
to normal?

Kind regards
Thomas Rupp
Vorarlberger Illwerke AG
MAIL:   thomas.rupp AT illwerke DOT at
TEL:    ++43/5574/4991-251
FAX:    ++43/5574/4991-820-8251



------------------------------------------------------------------------------------------
Dieses eMail wurde auf Viren geprueft.
Dieses eMail wurde auf Viren geprueft.

Vorarlberger Illwerke AG
------------------------------------------------------------------------------------------
=========================================================================