Hi All TSMers I'm Running TSM 4.2.2.12 on a Solaris 2.7 server (E250 400Mhz, 1GB mem). We have been having severe performance issues recently and moved our database volumes off onto a new disk. To do this we formatted a new db volume and copy, and then we deleted the original ones. TSM immediately went into action and moved the database volumes into the new volume.
The volume sizes were 5000Mb 2500Mb 1000Mb After they each finished there was a summary that showed number of bytes moved. In this case the results were as follows:- 5000Mb - 947,912,704 2500Mb - 2,621,440,000 1000Mb - 1,048,576,000 Now I can see that the figures for the 1000 and 2500 are correct, but the 5000 volume is way off! Any ideas why I am seeing this result. Is it just a bug or is the DB massively fragmented or something? Also, is there anyway to see if indeed the database is fragmented? Many thanks to all who help as this is very puzzling. All the best Farren Minns - John Wiley & Sons Ltd Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Cache Hit Percentage Since upgrading to TSM 5.1.6.2 on AIX 4.3.3 I have now noticed my cache hit percentage drops below 98% every day. Reset bufpool brings it back to 100.00% but after 24 hours it will again be below 98%. While on TSM 5.1.5.2 it was rarely below 98.5%. Has anyone else seen this behavior? Geoff Gill TSM Administrator NT Systems Support Engineer SAIC E-Mail: <mailto:[EMAIL PROTECTED]> [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (877) 905-7154
