[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 4573
  • Last Modified:

error e000e020 since daylight savings time change

Hello,

I found our backups did not run after daylight savings time with the following error in the logs:

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.

Even after I change the time window to be back an hour and set the start no later than time to allow 2 hours in the time window, I still get failures on the test run.  The log on the test run failure is very vague:

e0008703 - The test run has detected a potential problem. See the job log for details.
For additional information regarding this error refer to link V-79-57344-34563

I have looked at the link but it doesn't give any information that I can use.

Does anyone have any insight as to why this may still be failing even after the time window is changed?  The time on the server is correct and the backup device is accessible and has the correct time.

I have also cross posted this ad symantec, and found a couple of threads on this issue here however the link on how to use the no longer works and I am unfamiliar with bestop.bat.

I appreciate any help with this issue and thanks very much,

Maureen
0
maureen99
Asked:
maureen99
  • 4
  • 2
1 Solution
 
eagle-22Commented:
A couple things I would try:
1) Run Live update to install any latest updates or patches
2) stop all services and then restart them (making sure the time is correct on the server before hand).

0
 
maureen99Author Commented:
The time is correct on the server.  I ran live update and applied all the fixes that were out there.
Stopped the services and restarted them.

Still get the same results.

Another thread here indicated running BEutility.exe.  Should I be trying to run a repair on the database?
0
 
eagle-22Commented:
I would not try repairing the database at this point.
Can you run a test backup tathat will run 'Now', and not wait?

This sounds like an issue that Symantec may need to work on, others are also having this type of problem.
Are you able to expand the time frame window to more than the 2 hours?

Also, make sure you have enough space to run your backup or it may fail also (backup-to-diks folder space), or if using a Tape may check setting to 'Overwrite' tape (not append).
0
Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

 
maureen99Author Commented:
Thank you.

I checked the disk space to the NAS this is going to and there is enough.  
I tried running a test job "now" and it fails.
I can expand the time window to more than 2 hours

Unfortunately, we are a non-profit and got backup exec from techsoup.com so we can't call symantec for support.
0
 
maureen99Author Commented:
Can anyone tell me if I should be using beutility on the database?  It was recommended in a different thread on this error.
0
 
maureen99Author Commented:
I did a right click on one of the jobs and did a run now and the job ran.  After that the test run ran as well, and the jobs ran overnight.  

thanks alot for your help,

Maureen
0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now