Check your randomize setting with 'q stat'. By default it is 25%.

You can set it with set randomize.

bob

On Tue, Jul 09, 2002 at 01:33:40PM -0400, Martin, Jon R. wrote:
>         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