Hi,
I would appreciate help in the following situation. I tried to list all the relevant information and what I did.
DELL PowerEdge 1800, Small Business Server 2003, Backup Exec Ver 10.1 Rev 5629, Installed Updates: SP1 with Hotfixes 26, 27, 29, 33, 34. Using Removable Backup to Disk - Iomega REV.
This morning Backup Exec showed that my daily differential backup of last night is in Queued status, with no related active Alert/Error whatsoever. Here's what it showed in Job Monitor:
State: Active
Job Name: Differential Backup
Device Name: REV
Job Type: Backup
Job Status: Queued
Priority: Medium
Percent: N/A
Start Time: 9/14/2006 9:00 PM
Elapsed Time: 13:06:25
Byte Count: 12,422,418,597
As you can see, it actually ran because the byte count was not zero. This behavior has never happened before, and I suspect that it might have something to with Windows Updates that I installed on my SBS 2003 last night at 6:45 PM. The following updates were installed:
KB912442 - Security Update for Exchange Server 2003 SP2 - Non-cluster
KB916803 - Security Update for Exchange Server 2003 SP2 - Non-cluster
KB920685 - Security Update for Windows Server 2003
KB921883 - Security Update for Windows Server 2003
KB922582 - Update for Windows Server 2003
I searched on the internet and on veritas.com for any docs or KBs or discussion threads that might help with the Queued status, and nothing relevant is found. So, I proceeded to Cancel the job, and try to Run Now to see if it might work somehow or to see at exactly what point it turned into Queued status.
Instead the job failed with the following error: "Differential Backup -- The job failed with the following error: The Backup Exec job engine system service is not responding."
I stopped and restarted all Backup Exec services, then tried to Run Now again. This time it remains in Queued status, the elapsed time started counting, no active alerts/errors, but the byte count remains at 0. So, quite different from what I encountered in the first place.
I cancel that one and Run Now one more time, and this time it failed with job engine not responding error. Any subsequent cancel and Run Now produced the same error. I searched the error on the net and veritas.com and found many different suggested solutions, but they are mainly related to Ver 9.1. Therefore, I'm quite reluctant to try them without first hearing what this forum can offer.
In summary, the Windows Updates might have caused the ran-then-queued situation, but now there's also the problem with the job failing due to "The Backup Exec job engine system service is not responding".
Please help.
Thank you.
Henry
