Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

BE 12.5 takes 6 hours to start backup job

Updated: 27 May 2010 | 2 comments
shane.ede@firstcommunitycu.com's picture
0 0 Votes
Login to vote

We have a scheduled backup job that is scheduled to start at 12:01 am.  We've had to expand the window so that it completes, because it will not start the job any earlier than 6 am.  We've removed all pre-jobs and it still does it.  I've run out of ideas on how to fix this.  has any one else ran into it, or know of a fix for it?

Comments

CraigV's picture
19
Nov
2009
2 Votes +2
Login to vote

Hi Shane, What changed to

Hi Shane,

What changed to make it run this long?

What happens if you create another scheduled job and start it at 12:01AM? Have you maybe removed any servers from the LAN, but not the selection list (although that would just give you an error).

Laters!

If you find this is a solution, please mark it as such.

shane.ede@firstcommunitycu.com's picture
25
Nov
2009
0 Votes 0
Login to vote

ooops

Turns out one of the administrators had turned on time access, so the back up user was not allowed to log in to the server until 6 am so it would have never started before 6 am because it could not login.  Changed that and it runs fine.