We are having problems here with scheduled backups hanging. It happened on rare occassions prior to upgrading to 5.5.1, but it began happening with great frequency on certain Windows boxes after the upgrade. W2k3 servers with SP2, Broadcom NICs with the Advanced Control Suite, and a particular microsoft hotfix, 912222.
Management determined that we were not going to roll back the hotfix. The workaround that we used was to deselect the Advanced Control Suite TCP Chimney setting. Typically, our Windows folks blamed TSM because everything else was working fine, while we blamed Microsoft because TSM wasn't what changed, and TSM worked fine on unaltered Windows servers. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of Richard Sims Sent: Wednesday, February 18, 2009 8:23 AM To: [email protected] Subject: Re: [ADSM-L] TSM Scheduler service stops by itself On Feb 18, 2009, at 7:32 AM, admbackup wrote: > I am having a problem with the TSM Scheduler of a windows server. > It stops sometimes by itself in the middle of a backup of files. > The weird thing is that in the same server I have a scheduled TDP SQL > backup, but the scheduler service works without problem. You need to look for evidence. Inspect the dsmerror.log on the client, and the Activity Log on the TSM server for indications of cause. On a Windows box you can also check its Event Log, to see if the process is crashing, etc. Richard Sims IMPORTANT: E-mail sent through the Internet is not secure and timely delivery of Internet mail is not guaranteed. Legg Mason therefore, recommends that you do not send any action-oriented or time-sensitive information to us via electronic mail, or any confidential or sensitive information including: social security numbers, account numbers, or personal identification numbers. This message is intended for the addressee only and may contain privileged or confidential information. Unless you are the intended recipient, you may not use, copy or disclose to anyone any information contained in this message. If you have received this message in error, please notify the author by replying to this message and then kindly delete the message. Thank you.
