TSM-Client starts wrong scheduler
Have you checked the activity log. The AL would provide more information on what the problem might be. I addition to what others have suggested, is this a cluster node? Remember, for cluster nodes both nodes have to be set up exactly the same and you need to make sure the cluster resources are set up correctly. +-- |This was sent by romoja...@yahoo.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
TSM-Client starts wrong scheduler
Hi, since a few weeks we have a strange behaviour with one of our Backup-Clients. When the scheduler should start, the clients says that the scheduler is out of time and plans the next window start: 01/08/2009 21:03:50 --- SCHEDULEREC QUERY BEGIN 01/08/2009 21:03:50 --- SCHEDULEREC QUERY END 01/08/2009 21:03:50 Next operation scheduled: 01/08/2009 21:03:50 01/08/2009 21:03:50 Schedule Name: EVANPDC_DAILY_INCR 01/08/2009 21:03:50 Action:Incremental 01/08/2009 21:03:50 Objects: 01/08/2009 21:03:50 Options: 01/08/2009 21:03:50 Server Window Start: 00:00:00 on 01/09/2009 01/08/2009 21:03:50 01/08/2009 21:03:50 Scheduler has been stopped. now the scheduler should start: 01/09/2009 00:24:51 TSM Backup-Archive Client Version 5, Release 5, Level 1.0 01/09/2009 00:24:51 Querying server for next scheduled event. 01/09/2009 00:24:51 Node Name: ZENTGPFSDATA.EVA.MPG.DE 01/09/2009 00:24:51 Session established with server BACKUP: Windows 01/09/2009 00:24:51 Server Version 5, Release 4, Level 3.0 01/09/2009 00:24:51 Server date/time: 01/09/2009 00:24:49 Last access: 01/09/2009 00:15:21 but it just plans the next one: 01/09/2009 00:24:51 --- SCHEDULEREC QUERY BEGIN 01/09/2009 00:24:51 --- SCHEDULEREC QUERY END 01/09/2009 00:24:51 Next operation scheduled: 01/09/2009 00:24:51 01/09/2009 00:24:51 Schedule Name: EVANPDC_DAILY_INCR 01/09/2009 00:24:51 Action:Incremental 01/09/2009 00:24:51 Objects: 01/09/2009 00:24:51 Options: 01/09/2009 00:24:51 Server Window Start: 12:00:00 on 01/09/2009 01/09/2009 00:24:51 01/09/2009 00:24:51 Executing scheduled command now. 01/09/2009 00:24:51 ANS1814E Unable to start the scheduled event 'EVANPDC_DAILY_INCR' 01/09/2009 00:24:51 ANS1815E Either the window has elapsed or the schedule has been deleted But sometimes it works. That's very strange. Any ideas? TSM-Server version: 5.4.3.0 TSM-Server OS: Windows Server 2003 TSM-Client version: 5.5.1.0 TSM-Client OS: SLES 10 SP2 Best, Alex -- Mit besten Grüßen / Best Regards Alexander Födisch Max Planck Institute for Evolutionary Anthropology -Central IT Department- Deutscher Platz 6 D-04103 Leipzig Phone: +49 (0)341 3550-168 +49 (0)341 3550-154 Fax:+49 (0)341 3550-119 Email: foedi...@eva.mpg.de
Re: TSM-Client starts wrong scheduler
The first thing you need to look into is why your EVANPDC_DAILY_INCR schedule seems to be defined for a start time of midnight in one instance, and noon in another. Do you have something automated changing the schedule definition? I should think that a daily schedule would be defined to run once in a day, not multiple times. Review your TSM server Activity Log for what's going on. I'd also advise having your Windows boxes updated to sync to a time standard, given the time skew seen in the client session timestamps. Richard Sims
Re: TSM-Client starts wrong scheduler
Richard Sims pointed out the discrepancy between midnight and noon in your apparent scheduled start times, which is certainly worrying. I also notice that your scheduler is not starting up until almost 25 minutes after the scheduled start time. Why is that? If your startup window is short (say, 15 minutes), is it possible that your window really has elapsed, as the error message suggests? - Margaret Clark -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Alexander Födisch Sent: Friday, January 09, 2009 1:02 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM-Client starts wrong scheduler Hi, since a few weeks we have a strange behaviour with one of our Backup-Clients. When the scheduler should start, the clients says that the scheduler is out of time and plans the next window start: 01/08/2009 21:03:50 --- SCHEDULEREC QUERY BEGIN 01/08/2009 21:03:50 --- SCHEDULEREC QUERY END 01/08/2009 21:03:50 Next operation scheduled: 01/08/2009 21:03:50 01/08/2009 21:03:50 Schedule Name: EVANPDC_DAILY_INCR 01/08/2009 21:03:50 Action:Incremental 01/08/2009 21:03:50 Objects: 01/08/2009 21:03:50 Options: 01/08/2009 21:03:50 Server Window Start: 00:00:00 on 01/09/2009 01/08/2009 21:03:50 01/08/2009 21:03:50 Scheduler has been stopped. now the scheduler should start: 01/09/2009 00:24:51 TSM Backup-Archive Client Version 5, Release 5, Level 1.0 01/09/2009 00:24:51 Querying server for next scheduled event. 01/09/2009 00:24:51 Node Name: ZENTGPFSDATA.EVA.MPG.DE 01/09/2009 00:24:51 Session established with server BACKUP: Windows 01/09/2009 00:24:51 Server Version 5, Release 4, Level 3.0 01/09/2009 00:24:51 Server date/time: 01/09/2009 00:24:49 Last access: 01/09/2009 00:15:21 but it just plans the next one: 01/09/2009 00:24:51 --- SCHEDULEREC QUERY BEGIN 01/09/2009 00:24:51 --- SCHEDULEREC QUERY END 01/09/2009 00:24:51 Next operation scheduled: 01/09/2009 00:24:51 01/09/2009 00:24:51 Schedule Name: EVANPDC_DAILY_INCR 01/09/2009 00:24:51 Action:Incremental 01/09/2009 00:24:51 Objects: 01/09/2009 00:24:51 Options: 01/09/2009 00:24:51 Server Window Start: 12:00:00 on 01/09/2009 01/09/2009 00:24:51 01/09/2009 00:24:51 Executing scheduled command now. 01/09/2009 00:24:51 ANS1814E Unable to start the scheduled event 'EVANPDC_DAILY_INCR' 01/09/2009 00:24:51 ANS1815E Either the window has elapsed or the schedule has been deleted But sometimes it works. That's very strange. Any ideas? TSM-Server version: 5.4.3.0 TSM-Server OS: Windows Server 2003 TSM-Client version: 5.5.1.0 TSM-Client OS: SLES 10 SP2 Best, Alex -- Mit besten Grüßen / Best Regards Alexander Födisch Max Planck Institute for Evolutionary Anthropology -Central IT Department- Deutscher Platz 6 D-04103 Leipzig Phone: +49 (0)341 3550-168 +49 (0)341 3550-154 Fax:+49 (0)341 3550-119 Email: foedi...@eva.mpg.de
Re: TSM-Client starts wrong scheduler
Greetings, Have you checked to verify that the TSM server and the TSM client have exactly the same time? Is it possible that the TSM server has the correct time, and the TSM client's time was set incorrectly, and is exactly 12 hours off? Or it has the correct apparent time, but is set to the wrong time zone, making it effectively 12 hours off? I have seen backup schedules appear to start, then miss for this reason. It also looks like you are using schedmode polling, which is why it is starting 25 minutes after the actual start time. This is not a problem, but it explains the behaviour. Best Regards, John D. Schneider Phone: 314-364-3150 Cell: 314-750-8721 Email: john.schnei...@mercy.net -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Clark, Margaret Sent: Friday, January 09, 2009 11:39 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM-Client starts wrong scheduler Richard Sims pointed out the discrepancy between midnight and noon in your apparent scheduled start times, which is certainly worrying. I also notice that your scheduler is not starting up until almost 25 minutes after the scheduled start time. Why is that? If your startup window is short (say, 15 minutes), is it possible that your window really has elapsed, as the error message suggests? - Margaret Clark -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Alexander Födisch Sent: Friday, January 09, 2009 1:02 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM-Client starts wrong scheduler Hi, since a few weeks we have a strange behaviour with one of our Backup-Clients. When the scheduler should start, the clients says that the scheduler is out of time and plans the next window start: 01/08/2009 21:03:50 --- SCHEDULEREC QUERY BEGIN 01/08/2009 21:03:50 --- SCHEDULEREC QUERY END 01/08/2009 21:03:50 Next operation scheduled: 01/08/2009 21:03:50 01/08/2009 21:03:50 Schedule Name: EVANPDC_DAILY_INCR 01/08/2009 21:03:50 Action:Incremental 01/08/2009 21:03:50 Objects: 01/08/2009 21:03:50 Options: 01/08/2009 21:03:50 Server Window Start: 00:00:00 on 01/09/2009 01/08/2009 21:03:50 01/08/2009 21:03:50 Scheduler has been stopped. now the scheduler should start: 01/09/2009 00:24:51 TSM Backup-Archive Client Version 5, Release 5, Level 1.0 01/09/2009 00:24:51 Querying server for next scheduled event. 01/09/2009 00:24:51 Node Name: ZENTGPFSDATA.EVA.MPG.DE 01/09/2009 00:24:51 Session established with server BACKUP: Windows 01/09/2009 00:24:51 Server Version 5, Release 4, Level 3.0 01/09/2009 00:24:51 Server date/time: 01/09/2009 00:24:49 Last access: 01/09/2009 00:15:21 but it just plans the next one: 01/09/2009 00:24:51 --- SCHEDULEREC QUERY BEGIN 01/09/2009 00:24:51 --- SCHEDULEREC QUERY END 01/09/2009 00:24:51 Next operation scheduled: 01/09/2009 00:24:51 01/09/2009 00:24:51 Schedule Name: EVANPDC_DAILY_INCR 01/09/2009 00:24:51 Action:Incremental 01/09/2009 00:24:51 Objects: 01/09/2009 00:24:51 Options: 01/09/2009 00:24:51 Server Window Start: 12:00:00 on 01/09/2009 01/09/2009 00:24:51 01/09/2009 00:24:51 Executing scheduled command now. 01/09/2009 00:24:51 ANS1814E Unable to start the scheduled event 'EVANPDC_DAILY_INCR' 01/09/2009 00:24:51 ANS1815E Either the window has elapsed or the schedule has been deleted But sometimes it works. That's very strange. Any ideas? TSM-Server version: 5.4.3.0 TSM-Server OS: Windows Server 2003 TSM-Client version: 5.5.1.0 TSM-Client OS: SLES 10 SP2 Best, Alex -- Mit besten Grüßen / Best Regards Alexander Födisch Max Planck Institute for Evolutionary Anthropology -Central IT Department- Deutscher Platz 6 D-04103 Leipzig Phone: +49 (0)341 3550-168 +49 (0)341 3550-154 Fax:+49 (0)341 3550-119 Email: foedi...@eva.mpg.de This e-mail contains information which (a) may be PROPRIETARY IN NATURE OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) is intended only for the use of the addressee(s) named above. If you are not the addressee, or the person responsible for delivering this to the addressee(s), you are notified that reading, copying or distributing this e-mail is prohibited. If you have received this e-mail in error, please contact the sender immediately.
