Hi christo, this is question to improve my english:
> My backups are scheduled to start at 01:00, but didn't start till 02:41 > Monday & 01:21 today. Any idea why? Does it tell the schedule did run at 02:41 for sure or is this only a probable explanation? regards Juraj -----Urspr�ngliche Nachricht----- Von: Christo Heuer [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 10. M�rz 2004 10:45 An: [EMAIL PROTECTED] Betreff: Re: TSM Scheduling Simple answer - the fact that the schedule actually ran means there IS an association - the fact that it does not run at the set time has to do with the schedule randomization % that is set on the TSM server and the length of the start-up window for the schedule for this client. Simple example: Schedule randomization=25% Length of start-up window is 1 hour. Client schedule is set at 01:00. The randomization will cause the schedule to physically kick off anywhere between 01:00 and 01:15. (25% of hour). Hope this explains it. Cheers Christo ========================================================== If it happens to me I know I have forgotten again to define an association. Check with Q EVE whether you really have your schedules scheduled. If not, search after an error in your schedule /associations definitions. If yes, search after an error in Q ACTL and in dsmsched.log,dsmerror.log on your clients - assuming your client tsm schedulres are running at all :-) regards Juraj -----Urspr�ngliche Nachricht----- Von: VANDEMAN, MIKE (SBCSI) [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 10. M�rz 2004 02:31 An: [EMAIL PROTECTED] Betreff: TSM Scheduling My backups are scheduled to start at 01:00, but didn't start till 02:41 Monday & 01:21 today. Any idea why? Mike Vandeman 510-784-3172 UNIX SSS > (888) 226-8649 - SSS Helpdesk > > ______________________________________________ E-mail Disclaimer and Company Information http://www.absa.co.za/ABSA/EMail_Disclaimer
