Only this schedule has a priority of 'one', it is for testing the backup of one specific filesystem. There were no other events scheduled to run at this time, however, since the backup of this filesystem takes 14 hours (4.2 million objects/ 108 Gb) I assigned it higher priority over events occurring later in the day.
Randomization is probably the answer. I did not realize that randomization would be used when no other sessions/processes were active on the TSM Server and/or client. Thanks, Jon Martin -----Original Message----- From: Schaub Joachim Paul ABX-PROD-ZH [mailto:[EMAIL PROTECTED]] Sent: Thursday, July 11, 2002 6:44 AM To: [EMAIL PROTECTED] Subject: AW: Delayed Schedule Start your sched has priority 1, does all the other scheds have the same priority? If yes, why? greets joachim -----Ursprüngliche Nachricht----- Von: Jon Adams [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 10. Juli 2002 17:27 An: [EMAIL PROTECTED] Betreff: Re: Delayed Schedule Start Perhaps a combination of the randomization, the backup window or the available sessions at the time of backup? If there are no sessions available, the backup will start anytime a session is available within that schedule window. Jon Adams Systems Engineer IT IPS, Premera Blue Cross -----Original Message----- From: Etienne Brodeur [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 09, 2002 11:49 AM To: [EMAIL PROTECTED] Subject: Re: Delayed Schedule Start What's your Schedule Randomization percentage and what is the backup window for this schedule? If I recall correctly randomization is for every schedule even if it only runs on one node. And the ramdomization starts from the moment the nodes connect to the server not from the start of the window. backup window is 4 hours. schedule starts at 1 AM randomization is set to 25% node connects at 230 AM schedules will start between 230 and 330 AM. Could this be it? Etienne Brodeur "Martin, Jon R." <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 07/09/2002 01:33 PM Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject: Delayed Schedule Start The below schedule was scheduled for 1 PM. The client scheduler is polling and at 1:05 PM it updated, and said the schedule would start in 33 minutes. What causes a schedule to execute a time later than scheduled? I am aware of staggered starts for scheduled events, but this is the only thing scheduled at this time and nothing else is running on the server. Any ideas? Thanks, Jon Martin Policy Domain Name: SOLARIS Schedule Name: REBUILD_MR Description: Daily backup for Solaris Clients Action: Incremental Options: Objects: /rebuild_mr/ATX1/ Priority: 1 Start Date/Time: 05/16/01 13:00:00 Duration: 12 Hour(s) Period: 1 Day(s) Day of Week: Tuesday Expiration: Last Update by (administrator): ADMIN Last Update Date/Time: 07/09/02 10:57:07 Managing profile: 07/09/02 13:05:12 ------------------------------------------------------------ 07/09/02 13:05:12 Schedule Name: REBUILD_MR 07/09/02 13:05:12 Action: Incremental 07/09/02 13:05:12 Objects: /rebuild_mr/ATX1/ 07/09/02 13:05:12 Options: 07/09/02 13:05:12 Server Window Start: 13:00:00 on 07/09/02 07/09/02 13:05:12 ------------------------------------------------------------ 07/09/02 13:05:12 Command will be executed in 33 minutes. 07/09/02 13:05:12
