Hi Raymond, I had a similar issue using the latest 5.3.2 client. The OFS support was already configured in the previous version of the BA client (5.3.0.15), although it didn't work yet on Windows2003. The server was powered off and on again. I've placed the snapshotcachelocation in comment in the dsm.opt file and did a new test backup. The VSS (volume shadow copy service) is now used by the TSM client too to backup open files (eg the classic ntuser.dat / ntuser.dat.log / usrclass.dat / usrclass.dat.log of a logged on user). If the OFS is removed again, the VSS service is not being used at the start of a backup. So installing the OFS agent without an entry of the snapshotcachelocation in the dsm.opt file resulted in a successfull backup on Windows2003 using the VSS service of Windows to handle open files. All this was done on a test server and the setup was repeated on a few other servers, all going well so far. I've used the VSS feature of Windows2003 quit a lot with another backup solution and it even took a consistent backup of an Oracle9i RAC database and an Exchange 2003 mail server. So the VSS feature is doing t's job for 'open' files. For applications like Oracle and Exchange the specif agent should be used of course, it was just a stress test for the VSS backup. hope this helps, Kurt
________________________________ Van: ADSM: Dist Stor Manager namens Prather, Wanda Verzonden: vr 21/10/2005 21:21 Aan: ADSM-L@VM.MARIST.EDU Onderwerp: Re: [ADSM-L] 100% utilization on a windows 2003 server sp1 with TMS 5.3 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:[EMAIL PROTECTED] On Behalf Of Raymond Sent: Thursday, October 20, 2005 8:02 PM To: ADSM-L@VM.MARIST.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
