03-29-2011 03:23 AM
3x Backup Exec 12 SP5 on Windows Server 2003
1x Backup Exec 12.5 SP4 on Windows Server 2003
1x Backup Exec 12.5 SP3 on Windows Server 2008
9x Backup Exec 2010 SP1 on Windows Server 2003
3x Backup Exec 2010 SP1 on Windows Server 2008
17 different servers using 3 different versions of Backup Exec on 2 different versions of Windows Server in 5 different domains. All scheduled unlocks, inventories and backups have not run and are reporting as missed since clocks went forward from Greenwich Mean Time (GMT) to British Summer Time (BST) on 27/03/2011. Elapsed Time is zero. 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. “
All servers syncing to time.windows.com and have automatically gone forward one hour.
All servers have Regional Options set to English (United Kingdom).
All instances of Backup Exec set to LiveUpdate weekly on Sunday at 22.00.
This is recorded as a known issue on older versions of Backup Exec but not 2010:
http://www.symantec.com/business/support/index?page=content&id=TECH50983
I have restarted all the Backup Exec services as suggested and will check the scheduled jobs tonight.
Incidentally on 4 other servers the scheduled jobs ran as usual:
Backup Exec 9.1 on Windows Server 2000
Backup Exec 9.1 on Windows Server 2003
Backup Exec 10d on Windows Server 2003
Backup Exec 12 on Windows Server 2003 (server restarted at weekend)
I have created a reminder to restart all the Backup Exec services on 30/10/2011 (end of BST) just in case but would prefer an actual software fix.
Has anyone else experienced this or have any suggestions how to prevent it from recurring?
03-29-2011 03:57 AM
Similar forum posting:
http://www.symantec.com/connect/forums/backup-schlaegt-nach-sommerzeit-umstellung-fehl-e000e020
references updated knowledge base article:
http://www.symantec.com/business/support/index?page=content&id=TECH61668
which shows this is still an issue in Backup Exec 2010, despite this KB advising it's fixed in 11d :
http://www.symantec.com/business/support/index?page=content&id=TECH50983
The clocks change twice a year, every year. How has this not been fixed in 5 versions of the software?
03-29-2011 07:21 AM
Just had exactly the same on Backup Exec 2010 R2 SP1
Come on Symantec it's not the 80s
Cheers
Matt
03-31-2011 07:43 AM