Backup jobs stay in a Queue state for a long time.

Question

Hi allWe have a problem to execute the backup jobs from a BE appliance console.All jobs stay in an "Active:Queued" for a long time and don't transfer any data.The jobs are send to deduplication disk storage.&nbsp;We can review the TN:https://www.veritas.com/content/support/en_US/article.100007231but not "po_list_2" are present on the&nbsp;Deduplication Storage Folder Path\databases\catalog.Also review the TN:https://www.veritas.com/support/en_US/article.100010408but no "*.lck" files are present.Thanks in advance for your help.

riyaj_s · Answer

Please check if there is enough space available on Deduplication drive and it is not full. Incase of lower disk space run manual space reclaimation :&nbsp;https://www.veritas.com/support/en_US/article.100008765
Thanks and Regards

antonio_castro · Answer

Hi RiyajThanks for your answer but the space is not the problem; the disk is at 50% of occupation.Any other idea?Thanks for your support.

keith---- · Answer

Antonio,Is this still an issue, and is the SQL Server service using a lot of CPU while the jobs are queued?&nbsp;

milindp · Answer

Can you run an inventory on teh Deduplication folder and check if you see any errors?&nbsp;What is the version if Backup Exec?Is this BE Appliance?&nbsp;

antonio_castro · Answer

Hi KeithYes, we have yet the issue.But I review and the SQL service is not using a significant CPU, the resource monitor don't show us any anormal usage.Thanks for your help.

Forum Discussion

Backup jobs stay in a Queue state for a long time.

7 Replies

Related Content

All drives in active state,but jobs in queue state

EV11 Storage Queue

Extend expiration of VMWare application state capture

System state backup error

Adobe freehand objects with .fh* not handled in Storage Queue

Recent Discussions

Backup Exec Job got canceled

BackupExec for Oracle 23ai?

Add Oracle DB in Backup Exec

Veritas Backup Exec version upgrade & migrate to another new Server

Veritas Backup Exec 23 - Slow Backup after Windows server 2019 upgrade