Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

9.1 Backup Job Queues On Loading Media

Created: 13 Jan 2005 • Updated: 21 May 2010 | 2 comments
Anonymous's picture

I am using 9.1 4691 which has been patched with sp1 and sp2 and straing afterloading the media the job goes to queued.Please can anyone assist

Comments 2 CommentsJump to latest comment

BobH's picture

I had a similar problem. All my backup jobs would immediately go to "Queued" and never run. I had to go into the media manager and set the tapes in my set to "Rotation - Full" instead of just "Scratch Media". I used to be able to just quick erase my new tape sets but it appears I have to do this additional step now for some reason.

Version 9.1 Rev 4691

Gauri Ketkar's picture

Hi

There are many reasons why a Backup Exec operation is queued and here are
some suggestions:
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.
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.
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.
When the server is paused the current tape operation will go to a queue
state this can be resolved by un-pausing the server.
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.
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.

For any further query do revert.

Thank you.

NOTE : If we do not receive your reply within two business days, this post would be marked "assumed answered" and would be moved to "answered questions" pool.