Henrik, >> so my questions are, is there a setting in 5.3.2.0 server that I can >> controll this, or is it a feature..?
This is controlled by the "queryschedperiod" setting, either in server, or in client's dsm.opt (server option is supposed to override the client option). Try to issue "q stat" on your server to find out what you have defined. However, if only some of your nodes are showing such a behavior, I would suspect something wrong on client side ... Good luck ! Cheers. Arnaud ****************************************************************************** Panalpina Management Ltd., Basle, Switzerland, CIT Department Viadukstrasse 42, P.O. Box 4002 Basel/CH Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01 Direct: +41 (61) 226 19 78 e-mail: [EMAIL PROTECTED] ****************************************************************************** -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Henrik Wahlstedt Sent: Wednesday, 16 November, 2005 09:28 To: [email protected] Subject: Dsmsched.log Hi, Every 2:nd minute or so my client will query the server for the next scheduled event. And it continues to do that for 4 hours after the backup completes successfull. 11/15/2005 22:03:16 --- SCHEDULEREC QUERY BEGIN 11/15/2005 22:03:16 --- SCHEDULEREC QUERY END 11/15/2005 22:03:16 Next operation scheduled: 11/15/2005 22:03:16 ------------------------------------------------------------ 11/15/2005 22:03:16 Schedule Name: W2K-DAILY-INCR-OS 11/15/2005 22:03:16 Action: Incremental 11/15/2005 22:03:16 Objects: 11/15/2005 22:03:16 Options: 11/15/2005 22:03:16 Server Window Start: 18:05:00 on 11/16/2005 11/15/2005 22:03:16 ------------------------------------------------------------ 11/15/2005 22:03:16 Waiting to be contacted by the server. 11/15/2005 22:04:02 Querying server for next scheduled event. 11/15/2005 22:04:02 Node Name: X 11/15/2005 22:04:02 Session established with server X: Windows 11/15/2005 22:04:02 Server Version 5, Release 3, Level 2.0 11/15/2005 22:04:02 Server date/time: 11/15/2005 22:04:02 Last access: 11/15/2005 22:03:16 Since I havent seen this before, I had to restore some old dsmsched.log files to se if it happened before...no i hadn´t. I see this behaviour on 5 test nodes, w2k or w2k3 with 5.3.2.0 client and one with 5.2.3.11. The issue started after I uppgraded the TSM server, (w2k3), to 5.3.2.0. So my questions are, is there a setting in 5.3.2.0 server that I can controll this, or is it a feature..? TIA Henrik ------------------------------------------------------------------- The information contained in this message may be CONFIDENTIAL and is intended for the addressee only. Any unauthorised use, dissemination of the information or copying of this message is prohibited. If you are not the addressee, please notify the sender immediately by return e-mail and delete this message. Thank you.
