Backup-to-Disk backup jobs stay "Queued" in the Activity Monitor and the job never runs.

book

Article ID: 100010408

calendar_today

Updated On:

Resolution

When Backup-to-Disk jobs run, a lock file (*.lck) is placed in the Backup-to-Disk folder to stop other jobs from writing to the Backup-to-Disk backup file (*.bak) at the same time (Figure 1).  

Figure 1
 



The *.lck file is removed after the Backup-to-Disk job completes, but if the Backup-to-Disk job does not get a chance to properly terminate, the *.lck file will remain in the Backup-to-Disk folder. This will cause all subsequent operations to go into a "queued" status indefinitely.

Follow the steps provided below to resolve this issue:

1.  Ensure there are no other jobs running and close the Backup Exec (tm) console.

2.  Stop all Backup Exec services

3.  Browse to the Backup-to-Disk folder and delete the *.lck file

4.  Start all Backup Exec services

5.  Re-run the Backup-to-Disk job(s)

 

 


Issue/Introduction

Backup-to-Disk backup jobs stay "Queued" in the Activity Monitor and the job never runs.