Video Screencast Help
Symantec Connect login will not be available from 7am-1pm PT, Saturday April 12th, estimated. During that time, you will not be able to log in or engage in any activity on the site such as posting, commenting, or voting. You can still view and search content. Sorry for the inconvenience.

Jobs stuck indefinitely in Queued Status

Created: 13 Jan 2014 | 3 comments

We have had an ongoing issue for about 2 months now, and since we have had a clean build (3 times now) for Backup Exec 2012. We have opened numerous cases with Symantec to resolve this, and they claim the first time that HotFix 209149 (see ) corrects the issue. The issue is also noted by seeing Robotic Element errors stating that OST media is full and it brings the "virtual" slot for the PureDisk or OST storage device offline. Restarting the services in BE only makes the problem worse and causes a snowball effect whereby jobs constantly error in the ADAMM log files. Essentially, the jobs never can get a concurrency/virtual slot and they stay Queued forever.

I have seen others on this Forum with this problem, and while the Forum administrator seems to mark them as "Solved", they are not - because I see the threads drop off with no resolution identified.

Are other people having this problem? If so, how are you overcoming it? Once it starts the environment is essentially dead in the water because the jobs never start (they sit Queued forever) - save for one concurrency which for our size environment is only 1/4 the need we have.

We use CAS and 4 MMS servers with 2008 R2 with all patches applied, PureDisk 32TB volume on each MMS, Data Domain OST connection to DD-670 OST with OST-Plug 2.62 (28TB), replicated catalogs, and duplicate jobs for optimized deduplication between MMSs. We run BE 2012 SP3 clean - we reinstalled with SP3 slipstreamed because Symantec said this problem could be fixed through database repair by them manually or by reinstall...we chose reinstall (even though they did offer to "fix" the issue with database repair). We chose reinstall to validate whether SP3 truly fixes the issue. It is clear to us it does not.

We are looking for anyone else who has had this problem to report into this forum.

Thank you,



Operating Systems:

Comments 3 CommentsJump to latest comment

Steven L.'s picture

Hi drmont1,

  Supposdly, Symantec silently changed the way they write data to the .bkf file in SP3.  I learned this while diving deep into my VSS issues...which you confirmed..(thanks).  Check with EMC DD to see if they have a codeset or firmware upgrade.


Snip3r6659's picture


I share your frustration in this.  we to have the same issue with jobs being stuck in queue.  Although it is a bit more random.  Sometimes i will come in and find that a job is stuck since the night before,  and i cancel it and it runs fine the next night!  sometimes,  recreating the job fixes the issue.  and in some cases nobody seems to know why it is stuck!

We to have done a clean build of our MMS putting it entirly on a stand alone server (symantec recomendation)  We had been using what Symantec called a non supported disc for our deduplication,  so we replaced it with a "supported" device.  although i highly doubt that makes any difference.  and neither of these suggestions have solved the issue.

We are preforming our backups to deduplication disc.  and they always seem to pick and choose who wants to stick on which night!  yet ive found that if i run a backup to disc on the same server that a deduplication job is stuck on,  it runs without an issue?

Frustrated and confused...  is there a patch for that?

kkoekkoek's picture

We've been having the same issue with a pretty similar setup. I actually found that disconnecting the MMS from the CAS and just running it in stand alone after running a re-inventory seems to make the issue go away but as soon as we reconnect it to the CAS it starts randomly queing jobs forever. So I'm pretty much no help but at least you know there's more frustrated users.