Forum Discussion

drmont1's avatar
drmont1
Level 3
11 years ago

Jobs stuck indefinitely in Queued Status

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 http://www.symantec.com/business/support/index?page=content&id=TECH204116  ) 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,

Dana

 

2012
Backing Up
Backup and Recovery
Backup Exec
Central Admin Server Option
Deduplication Option
Performance
Windows Server (2003-2008)

15 Replies

Sort By
Replies have been turned off for this discussion
  • Drgrant's avatar
    Drgrant
    Level 2
    9 years ago

    Why backup exec 2014 says active quered , please assist its running for ever.

  • JunkStuff997's avatar
    JunkStuff997
    9 years ago

    In my case, I  simply had to 'Respond OK' to the Active error alerts to get the Jobs to run. Unfortunately I wasted hours of trying different solutions. So make sure to check that FIRST.

  • SFEric's avatar
    SFEric
    10 years ago

    This can happen if the target backup device is stuck in "read-only" mode. Go into Storage, click on the device (not the pool, but the individual device), click Properties tab on left, and change "Limit operations to read-only" to no. Apply, retry, voila.

  • steve_prindevil's avatar
    steve_prindevil
    10 years ago

    I have a similar issue, but only when writing to disk backup. the backups to the Amazon VTL are working fine

  • dennisblotenbur's avatar
    dennisblotenbur
    Level 3
    10 years ago
    I have also the same issues as described in this request.. Is there already a solution to fix this?
  • dhansen10's avatar
    dhansen10
    Level 3
    10 years ago

    That's sad to hear that this wasn't corrected in 2014.  I've had this issue in the 2010 version and the eventual fix was to identify the bad pieces of media that it was trying to find and removing them through SQL.  Although I understand the concepts behind fixing it you need to pretty adept at using SQL and know how to identify the bad pieces of media.  It took me six months of working with support to finally get it escalated to the correct person, but once in his hands it was resolved somewhat quickly.  If you all continue to have these issues have you tried talking to the on-call duty manager or tried to get this escalated? Good luck and if not time to get rid of it.

  • Snip3r6659's avatar
    Snip3r6659
    Level 2
    10 years ago

    Jimmm,

    My problem still exists,  as does the circle of unrelaible help and support.  i have tried everything i can think of.  swymantec support has deleted my dedup disks 3 times now.  and it seems no matter how loud i yell nobody wants to take ownership of the issue.

    They implement a "fix"  and most times i never here back from the tech during the "report back" period.

    I have invested in backup exec consultants,  that look at our environment.  and to be honest im starting to look at alternate softwares.  i love backup exec but i feel like i am stuck in a loop,  and its not exactly comforting to see this many other users with the same issue still unresolved!

    unfortunatley i have nothing helpful to report.  as i find it difficult to even find reliable support tech that calls me back.

     

  • Jimmm's avatar
    Jimmm
    10 years ago

    No sure if this thread is still active, but i share the frustration of the above posters. I have been using Backup Exec since it ran on a Novell server & was made by Arcata.  Ever since the upgrade to 2012, then 2014, the platform has become so unreliable that I have almost lost confidence in Symantec's ability to fix it. 

    I am having the same Queue issue, as well as multiple external media issues, too numerous to detail in this post. When I talk to Symantec, their answer is always recreate the job, recreate the media, recreate the catalogs ... How about making a product that does not require constant fixing?  

    Please, someone tell me that I am mistaken & that there is a way to make this software reliable again. 

    Thanks, 

    Jim