In article <[EMAIL PROTECTED]>, Chris Hund <[EMAIL PROTECTED]> says: > Hello Chris
We have seen many strange things when backups run, it is just a good puzzle to find the root cause. We had one server that would pin one cpu in a dual cpu box during the backup. The TSM support folks came up with a trace that indicated which file tsm was working on. It turns out that when TSM tried to read t one file it's cpu usage would go to 100%. But it turns out that trying to read the file with notepad would get the same results. It was the Anti-virus software causing the problem, but they said that could not fix the problem. We deleted the file and all was well. Did you see anything in the windows event logs. Have you tried turning on the TSM trace flags to see if that tells you more.Tsm tech support should be able to tell you more from the trace. Can you run Task Manager and see who is using cpu and how much. You might also look at the free tools at www.sysinternals.com to trace file and registry access. >Hi all, > >Has anyone ever come across an issue where the Tivoli client locks up a Win2k >system? This is happening fairly regularly with one of the Win2k boxes in our >environment. > >Here are a few small excerpts from the dsmsched.log file during the times the >system locks up: >Chris Hund
