cancel
Showing results for 
Search instead for 
Did you mean: 

daylight saving time missed backup

cptjck25
Level 4

So when daylight savings time happen our backup job was missed and we go the error message

e000e020 - The Job was scheduled to run, but the availability window closed before the job could start. There may not have been any destination device available during the window, or the job may have been submitted to run when the window was closed. 

The start time for the was 3/11/2012 11:00pm and it missed.

Do have to reschedule  my jobs or was just a glitch.?

1 ACCEPTED SOLUTION

Accepted Solutions

Colin_Weaver
Moderator
Moderator
Employee Accredited Certified

The only permamanet fix for this issue is upgrading to BE2012, in any previous versions of BE, this problem will re-appear (each DST change) if you have limited time windows for your backup operations. - Note it can even appear a few weeks after the DST change if you have monthly jobs that could be affected.

Doing run now on the jobs or waiting for the next instance that the job should run anyway is the usual workaround for the issue.

View solution in original post

4 REPLIES 4

Backup_Exec1
Level 6
Employee Accredited Certified

Hi

Please check this

http://www.symantec.com/docs/TECH61668

 

Thanks

Sush---
Level 6
Employee Accredited Certified

Also to provide more information..... With the new Scheduler introduced in BE 2012, the Daylight Saving time issue where the backups used to be missed is now completely eliminated.

 

Thanks,

-Sush...

Peterhr
Not applicable

 

Media Server: Version 13.0 Rev. 5204 (32-bit)
Administration Console: Version 13.0 Rev. 5204 (32-bit)
Desktop and Laptop Option: Version 3.1 Rev. 3.46.06a 
 
Error: e000e020 - The job was scheduled to run, but the availability window closed before the job could start. There may not have been any destination devices available during the window, or the job may have been submitted to run when the window was closed.
 
Original start time : Tuesday, March 27, 2012 12:00:00 AM
Job started         : Monday, March 26, 2012 11:00:03 PM
 
UK Times - Clocks went to summer time Sunday
 
Time window is set to
Start no earlier than: 23:00:00
and no later than: 23:59:59
 
I suspect restarting the BE services would have fixed the issue for now - I rebooted the machine.

Colin_Weaver
Moderator
Moderator
Employee Accredited Certified

The only permamanet fix for this issue is upgrading to BE2012, in any previous versions of BE, this problem will re-appear (each DST change) if you have limited time windows for your backup operations. - Note it can even appear a few weeks after the DST change if you have monthly jobs that could be affected.

Doing run now on the jobs or waiting for the next instance that the job should run anyway is the usual workaround for the issue.