07-07-2011 04:39 PM
We are running Backup Exec 2010 locally on a Windows 2008 R2 with a single load LTO-5 tape drive attached. We do a full backup with verify Monday through Friday from the C: D: and E: drives and the system state to tape in that order. The backup has been running flawlessly beginning at 6:30 p.m. and ending before 9:00 p.m. from 4/8/2011 until 6/30/2011. On 7/4/2011 the job used the order of backup of E: and systemstate then, verify of C: D: E: and system state, then backup of C: and D:. This backup starts at 6:30 p.m. and finishes by 9:00 a.m. the next morning. There are no BEWS alerts just informational pieces. I have tried deleting then recreating the selection list, job policy and the scheduled job. It makes no difference. Is anyone able to explain what I need to do to regain control of the Backup Exec 2010 software.
07-07-2011 05:38 PM
Go through the job log and check which resources are taking long time to complete.
If possible compare the previous job logs with the latest onces.
Also make sure that there are no media remove alerts in the alerts tab.
07-07-2011 08:31 PM
On 7/4/2011 the job used the order of backup of E: and systemstate then, verify of C: D: E: and system state, then backup of C: and D:.
I don't understand. How can your job verify C: and D: before they are backed up? It makes no sense. Can you save the joblog as a mhtml file and post it here?
It could be that the BEDB is damaged. You can go to the BE installation directory and use BEUtility to repair the BEDB.