For Windows clients: I had a lot of problems with the service stopping using 5.1 TSM clients on Win2K. Sometimes it just died, all would die about once a month. I think at 5.1 there was a known memory leak; got better with 5.2, even better with the 5.3 client.
What I recommend is setting the Windows properties of the scheduler so that Windows will restart the service once or twice. In Control Panel -> Admin tools -> Services, Open Properties of the TSM Scheduler service, select the Recovery tab. Set it to restart after the 1st and second failure, do nothing after subsequent failures, restart fail count after 1 day. That way if the service dies due to the ever-present slow memory leak, Windows will restart it automatically. If they still fail, look at the Windows EVENT log and see if there is any indication of why, or a Windows error code, and report it to -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Meadows, Andrew Sent: Wednesday, January 04, 2006 11:19 AM To: ADSM-L@VM.MARIST.EDU Subject: Missed backups I have a general question here. I have about 150 clients. Client info: Windows 2003 server Windows 2000 server Red Hat Linux 3 AS AIX 5.1 All running tsm client version 5 or later sending data to a tsm server on AIX running version 5.3 On a nightly basis I have at least 6 or 7 of these servers that miss their backups due to the service stopping. Is this common. Do other people experience these misses or is it something I need to look into on these servers. For the most part they are not the same server and I have the schedules spread from 7pm to 12 pm hourly. Just wanting to get a general guage of if there is something that I need to look into that I am doing wrong or if this is a normal and acceptable level of misses per night. Thanks, Andrew ******************************************** This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please erase all copies of the message and its attachments and notify us immediately. Thank you. ********************************************
