Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

jobs stay in ready status 1

Status
Not open for further replies.

bnothos

Programmer
Nov 6, 2003
24
CA
I am runnning backupexec 9 for windows servers and my scheduled jobs wont run. They get to the state ready and just site there. The device is not paused and if I right click on the "stuck" job and do a test run, the test run will complete successfully. Inventories also work. If I tell the job to run now it does nothing. anyone know how to resolve this?

Thanks.
 
Sometimes I have the same experience with my autoloader. It's usually because something caused Veritas to 'lose' communications with the autoloader/tape drive.

Things to check:

1. Backup Exec: Devices tab. Is the device off-line?
2. Windows: device manager: are the tape drives listed?

If 2 is no, run Add/Remove Hardware. It will find the tape devices.

If 1 is yes, check #2. If #2 is no, try to bring the devices back online using Backup Exec.

You might also want to just stop the Backup Exec services. Reboot the tape devices/autoloader and restart Backup Exec services.

Lastly, you might try reloading the drivers.

-SQLBill
 
Thanks for the reply, but none of these solutions worked for my situation. All remains the same.
 
Well, I noticed that it thought that today's backup tape was a cleaing tape. I re-inventoried it and now it recognizes it correcly, but still the backup job is stuck in ready status...
 

Here's the problem and solution after much time investigating...

My company's tape robot had recently failed and they purchased a new unit. The previous administrator did not remove the old device from backupexec. The scheduled jobs were set to run on "All Devices" available on our backup server. For some reason this confused it. Event though the old device had it's status set to "offline" (it was physically no longer present) this seemed to confuse the software. I edited the job template that all the backups were created from to specifically use the new robot instead of the ambiguous "All Devices" selection and voila, the backups started working. The strangest thing about this problem was that inventories would still work regardless of the "All Devices" selection, it was just the physical backups that wouldn't run.
 
Hi bnothos,

I think I have a similar problem to the one that you have detailed in this thread. I've changed my jobs so specify the device they really should be using like you say so that should fix it for all future jobs. (Thanks for you advice on that.)

But I just wondered how you got rid of the already stuck job? because I've rebooted and stopped and started services and removed and added devices and it's still sitting there [sad]

Thanks
M
 
Mthales,

I bet this isn't the answer for you, but I simply cancelled the stuck jobs. There was no special trick.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top