DP >=10.00 disabling and enabling a schedule makes a job run immediately
When disabling a schedule and reenabling it the job starts with about a minute delay. We found out that this happens when a schedule has a start date in the past. One has to edit the schedule and set the start date in the future to avoid immediately starting of the assosiated job.
It's senseless to have the ability to disable jobs in the schedule overview when reenabling it would mean starting all assosiated jobs immediately after some delay.
Please don't let data protector think that it must catch up "missed" backup jobs from the past.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.