HOW did you get the server to install on XP?!? I would love to set up a test TSM server on an XP system, but when I tried it, it would not install there. (It is not supported on XP, according to the TSM site, so I didn't call support.) BUT, back to your question:
When I have seen strange behavior that locks up the machine during a client backup, it has always been due to the client backup of Windows System State. Nothing appears in the Event logs. A reboot usually fixes it, temporarily. Things to try: -If this happens EVERY time, try running a backup from the GUI. Select ONLY the LOCAL drives, not the SystemState. If that works OK, you can try again just the SystemState and see if that locks up, to prove the problem. -If it only happens occasionally, you can test by changing the scheduler so that it doesn't back up system state during a regular backup: domain -systemstate During the test you can back up system state using ntbackup instead, writing to a flat file, and let TSM back up the flat file. This is the command you use for a Windows scheduled task that does system state backup with ntbackup instead of tsm: C:\WINNT\system32\NTBACKUP.EXE backup systemstate /f c:\pathname\systemstate.bkf -The 5.3.4.3 client is REALLY REALLY new; in fact it is a patch, not a formal code release. I would not assume that ANYONE but you has tested that version on an XP system that is also running a TSM server! Perhaps you have found a problem with the patch! You could back off to the 5.3.4 level, or even the 5.3.2 level. -If you have implemented OpenFile support in the TSM client, TURN IT OFF. There have been many problems with open file support and Windows 2003; I'm sure they are in XP as well. Wanda -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, July 13, 2006 5:20 PM To: Prather, Wanda Subject: AW: [ADSM-L] TSM hangup of whole machine Wanda, yes the server is running on Windows XP, cause it is a very small installation without any Windows 2000 or 2003 available. So I'm forced to run the server under Windows XP. But the strange situation is, that the server is running for more the one year under different releases of TSM. And suddenly it has this strange behavior. Kind regards from Karlsruhe (Germany) Ronald -----Ursprüngliche Nachricht----- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Prather, Wanda Gesendet: Donnerstag, 13. Juli 2006 20:16 An: ADSM-L@VM.MARIST.EDU Betreff: Re: [ADSM-L] TSM hangup of whole machine Do you mean that your TSM server is running on Windows XP, not windows 2003? -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Ronald A. Hammer Sent: Thursday, July 13, 2006 9:17 AM To: ADSM-L@VM.MARIST.EDU Subject: TSM hangup of whole machine Hi Listers, I'm running TSM V5.3.3.2 with B/A client V5.3.4.3 under Windows XP SP2. The TSM server owns only a disk stgpool and do no migration to sequential media. Since a few days the backup of the TSM server itself results in a hang up of the whole machine. All backups of the other clients (V5.3.4.0) running perfectly. In the act log of the server, in dsmsched.log and dsmerror.log and in the event logs of Windows XP I can't find anything that points to that problem. Does anybody have a idea what I can do to prevent that in the future. Thanks in advance Ronald
