BE 2010R2 Job Status "Queded" > no indication of why...

[Edward_Charles]

On various occasions we find our job status staying in queued mode.

The question is is there any way of finding out WHY? We've never been able to determine why or what it's waiting for so we usually end up cancelling the job. Trying it again to confirm it'll work at night and not stay queued all night.

Any thoughts would be appreciated.

Thank you.

[Kiran_Bandi]

Check for any alerts waiting for response, under alerts tab.

Is it a B2D job or B2T? Disk space or idle devices also can cause this. No idle devices are available status will be displayed in the job monitor in that case.

Regards...

[Riyaj_S]

This issue is resolved in Backup Exec 2010 R3 hotfix 159965.

http://www.symantec.com/docs/TECH160915

[Edward_Charles]

Thanks guys for your reponses. There aren't any related alerts that need to be responded to. We always just end up cancelling the job and trying again. Many times it goes into queued state again. Sometimes it helps if we recreate the (removable) B2D folder but again we have no indication. We're just using B2D jobs (no tapes) some for LAN backups and some using the device pool. It's not lack of space because if that was they case as sometimes happens if it fails to overwrite we get the "out of free space" alert.

Since we're running 2010 R2 should we just upgrade to R3? Do we then still require to add this hotfix of will the latest R3 have this already included?

The hotfix article is also talking about deduplication jobs in queued state but we're not using that.

Thoughts would be appreciated.

Thank you.

[pkh]

If you are using USB disks, you should be using normal B2D folders.  Removable B2D folders are meant for things like RDX and Jaz drives.

[CraigV]

Hi,

If you can do the upgrade, then why not? R3 fixes a number of issues over previous versions, so it is worth a try. You wouldn't need to install the HF...R3 SHOULD in theory include it already as part of the application.

The upgrade is straight-forward...download the ISO and either write to a DVD or mount with an ISO application.

Stop your BE services and grab a copy of the Data/Catalogs folders in case anything happens during the upgrade.

Run the upgrade and you can use your existing license keys. Once done, run LiveUpdate and update the media server before running a push-install to any remote servers you might have.

You can download R3 from the link below:

https://www4.symantec.com/Vrt/offer?a_id=93355

Thanks!

[be-nugget]

If you are savvy with the debug monitor this can sometimes help find out why a job is queued without a reason or alert.

[Edward_Charles]

Thanks for the replies.

We're not familiar with the debug monitor, how does it work?

Thank you

[Edward_Charles]

I've heard everyone is using USB disks instead of SATA disks?

Anyways we used to use the removable B2D folders yes (with not to many problems) but now we're trying to use the normal B2D folders in a device pool instead.

Thanks

[Edward_Charles]

Update, we just upgrade to R3 with all the live updates but so far I haven't seen any different behaviour (compared to R2) and the Device Pool still makes all devices online vs just the one that's actually online...

As mentioned it then creates all the extra B2D folders automatically and of course then that actual path becomes online. The problem then is when running a job to that device pool it stays in queud mode because I guess it doesn't know which path to backup to since all are avaible??

Please help, does Symantec have a solution/work around coming?

Thank you

[pkh]

You can enable the debug more using the procedure below

http://www.symantec.com/docs/TECH23853

Note that the log can be voluminuous so turn off debug as soon as it is not needed.