Video Screencast Help

Job always queued

Created: 21 Jan 2005 • Updated: 21 May 2010 | 6 comments
Stu's picture

Backup Exec 9.1 for Windows Servers
Windows 2003 SBS Server
Certrance tape drive

The backup job status immediately becomes Queued even though no other jobs are running. Test runs complete successfully but normal jobs get stuck.

What has happened to Veritas' email support? Can I send anyone event logs or BEdiag files?

Comments 6 CommentsJump to latest comment

anoop nair 2's picture

Hi,

There are many reasons why a Backup Exec 9.x operation is queued and here are some suggestions:

1. Verify that the media sets exist, both existing and newly created. Do an inventory of all the tape(s) and find out if they belong to any particular media set or to the foreign media category. If the media selected to perform a backup or restore operation does not belong to either the default media set or scratch media, all operations will display the "Queued" status. To resolve this, either erase the media or move it to an appropriate media set.

2. When a job is manually started using the Run Now option, it could display the "Queued" or "Pending" status. This occurs due to the recent changes in the system time and date and can be resolved by restarting the Backup Exec services.

3. Jobs could be locked in a pending state if the tape device drivers or the tape device has changed, or Backup Exec has been upgraded. To resolve this issue, disable and remove the device from the Devices tab, and then restart the Backup Exec services.

4. When the server is paused the current tape operation will go to a queue state this can be resolved by un-pausing the server.

5. When the Shared Storage Option (SSO) is installed, jobs may go to a pending state because a job has been sent to a device that does not have an active fiber connection to the backup server.

6. Jobs could be set to a pending state if the small computer system interface (SCSI) device times out. To verify the device timeouts, view the "Event Viewer System" log. Errors reported are event IDs of 7, 9, 11, or 15. SCSI timeouts will cause the SCSI bus to reset and this makes all the devices on the SCSI bus to abort their current command. The job in the pending state must be aborted. To abort the job right-click on the job in the Activity Monitor and select Cancel. If the job does not cancel with a small duration of time (which could be between 1 to10 minutes), stop all of the Backup Exec Services (this may take some time depending on the amount of time the SCSI devices takes to timeout). Any further device operations will need to follow the resolution of the SCSI timeout errors.

Please refer to the following technotes for troubleshooting and further information:


http://seer.support.veritas.com/docs/191158.htm

http://seer.support.veritas.com/docs/248709.htm

Sagar Kamat 2's picture

Please let us know whether the issue has resolved.

Stu's picture

Thank you I'll give all your suggestions a go!

Zerene Sangma's picture

Do let us know if the issue is resolved.

Vidyaj  Patnekar's picture

Hope the issue is resolved.Kindly let us know if not.