Server: AIX TSM 5.2.4.5
Client: TSM 5.3.0.5

We have the same problem some times on big file server (10 millions).
For us, the problem is tied with the Journal. When the journal is
"crashed" (too many entries), the following backup is locked with 100%
CPU utilization. (You could track this state in Windows Event Log).

If you have the same problem: to force reset of the journal, you could
validate your policy set or stop your TSM Journal and delete Journal
files and restart after.

Prather, Wanda wrote:

I have about a dozen Win2k3 machines with SP1; backing up with TSM
5.3.0.8 client.
Have never had this problem.


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Raymond
Sent: Thursday, October 20, 2005 8:02 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: 100% utilization on a windows 2003 server sp1 with TMS 5.3


Dear TSM Guru's,



I am totaly new on TSM. At the moment we are running Windows 2003 server
with SP1 on it. We have a diskpool at a SAN. The diskpool is configured
in
his own Array, the Array is about 400 GB.



TSM 5.3 is installed with latest Service patches so also Open File
option
will work with windows 2003. When we schedule a backup with tsm the
Windows
2003 server is getting locked up with a 100% utilization. I first tought
it
was my Virusscanner so i disabled all services but its not the
Virusscanner.
When i am connected to the machine trying to backup with RDP, I notice
that
my session is getting locked. When i logoff from the machine, I can't
connect again.



You are still able to give a network ping to the machine but no RDP is
possible anymore, also when you look at jobs scheduled on the TSM
console
you also notice that no data is getting back tothe server. Only hard
reset
at the front of the machine will get you back up running.



Does anybody on this forum has same problems with TSM 5.3 with Windows
2003
server.



I hope somebody can answer me.



Regards,



Raybonl