The normal BA client dsmsched.log is in a different directory - this is definitely only the TDP scheduler.
I don't think the summary table records client schedule queries.. On Wed, Jul 15, 2009 at 2:46 PM, Huebschman, George J. < [email protected]> wrote: > Is it possible that a manual backup was run before the scheduled backup? > Manual backups do not normally update to the dsmsched.log, but they do > count against the daily record of backup events. > > What is in your summary table? > > George H. > > -----Original Message----- > From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of > Tchuise, Bertaut > Sent: Wednesday, July 15, 2009 9:21 AM > To: [email protected] > Subject: Re: [ADSM-L] Schedule jump > > Matthew, > > When you restart the TSM Central Scheduler for the TDP client, do you > still have the same issue? It is possible that the TUES_INCR schedule > was disassociated from the QBCWSWIEPOO1-EXC client; it is possible that > the schedule was renamed, check the schedule associations for the > specific client. If non conclusive, was the time changed on the client? > Check the event log for any clue. > > Good luck. > > BERTAUT TCHUISE > Storage Support Administrator > Legg Mason Technology Services > *410-580-7032 > [email protected] > > > -----Original Message----- > From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of > Matthew Large > Sent: Wednesday, July 15, 2009 8:05 AM > To: [email protected] > Subject: [ADSM-L] Schedule jump > > Hi, > > this is a strange one - see the dsmsched.log extract below - at 15:28 > the 'next schedule' was queued up for 20:00 last night (TUE_INCR), but > by 16:28 it had decided that it was instead going to run the WED_INCR > tomorrow instead, thereby ignoring last night's schedule. > > I've not seen this behaviour before - is there a reason for it? I > guarantee nothing was changed on the server. > > 07/14/2009 15:28:46 > ------------------------------------------------------------ > 07/14/2009 15:28:46 Schedule Name: TUE_INCR > 07/14/2009 15:28:46 Action: Command > 07/14/2009 15:28:46 Objects: "C:\Program > Files\Tivoli\TSM\TDPExchange\tdpexcc.exe" BACKUP * INCREMENTAL > 07/14/2009 15:28:46 Options: > 07/14/2009 15:28:46 Server Window Start: 20:00:00 on 07/14/2009 > 07/14/2009 15:28:46 > ------------------------------------------------------------ > 07/14/2009 15:28:46 Schedule will be refreshed in 1 hour. > 07/14/2009 16:28:46 TSM Backup-Archive Client Version 5, Release 5, > Level > 0.4 > 07/14/2009 16:28:46 Querying server for next scheduled event. > 07/14/2009 16:28:46 Node Name: GBCWSWIEP001-EXC > 07/14/2009 16:28:47 Session established with server SWISP001: Solaris > SPARC > 07/14/2009 16:28:47 Server Version 5, Release 5, Level 0.3 > 07/14/2009 16:28:47 Data compression forced on by the server > 07/14/2009 16:28:47 Server date/time: 07/14/2009 16:28:27 Last > access: > 07/14/2009 15:28:25 > > 07/14/2009 16:28:47 --- SCHEDULEREC QUERY BEGIN > 07/14/2009 16:28:47 --- SCHEDULEREC QUERY END > 07/14/2009 16:28:47 Next operation scheduled: > 07/14/2009 16:28:47 > ------------------------------------------------------------ > 07/14/2009 16:28:47 Schedule Name: WED_INCR > 07/14/2009 16:28:47 Action: Command > 07/14/2009 16:28:47 Objects: "C:\Program > Files\Tivoli\TSM\TDPExchange\tdpexcc.exe" BACKUP * INCREMENTAL > 07/14/2009 16:28:47 Options: > 07/14/2009 16:28:47 Server Window Start: 20:00:00 on 07/15/2009 > 07/14/2009 16:28:47 > ------------------------------------------------------------ > 07/14/2009 16:28:47 Schedule will be refreshed in 1 hour. > 07/14/2009 17:28:47 TSM Backup-Archive Client Version 5, Release 5, > Level > 0.4 > 07/14/2009 17:28:47 Querying server for next scheduled event. > 07/14/2009 17:28:47 Node Name: GBCWSWIEP001-EXC > 07/14/2009 17:28:48 Session established with server SWISP001: Solaris > SPARC > 07/14/2009 17:28:48 Server Version 5, Release 5, Level 0.3 > 07/14/2009 17:28:48 Data compression forced on by the server > 07/14/2009 17:28:48 Server date/time: 07/14/2009 17:28:27 Last > access: > 07/14/2009 16:28:27 > > IMPORTANT: E-mail sent through the Internet is not secure. Legg Mason > therefore recommends that you do not send any confidential or sensitive > information to us via electronic mail, including social security > numbers, account numbers, or personal identification numbers. Delivery, > and or timely delivery of Internet mail is not guaranteed. Legg Mason > therefore recommends that you do not send time sensitive or > action-oriented messages to us via electronic mail. > > 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. > > IMPORTANT: E-mail sent through the Internet is not secure. Legg Mason > therefore recommends that you do not send any confidential or sensitive > information to us via electronic mail, including social security numbers, > account numbers, or personal identification numbers. Delivery, and or timely > delivery of Internet mail is not guaranteed. Legg Mason therefore recommends > that you do not send time sensitive > or action-oriented messages to us via electronic mail. > > 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. >
