Backup 9.1 Exec jobs no longer start

[captaincrunch00]

Hi there, 2003 server running BE 9.1.

I have jobs scheduled to start, they just simply dont start. I put in a tape and I try to inventory it and it sits there at "Ready" or if I get lucky it'll go to "Running" but then I can manually eject the tape and insert another tape, eject that one, put in another one... all day long and it will never actually run that job or read the tape at all.

Any ideas? I didnt install any MS Updates lately, I'm going through my logs checking that, but I'm like 99% sure I didnt install anything.

Thanks for any ideas!

 

[LawnBoy]

Any chance you have an alert pending somewhere? BE will wait for you to respond to an alert before it will do much of anything else.

 

[captaincrunch00]

I set them to autorespond OK to all alerts because I really dont care about them.

I've restarted the server a few times, restarted the services a few times, nada.

 

[LawnBoy]

Anything in the W2k3 Event Log? Checked your cabling? Sounds like the deck's just not responding. Got any diagnostics you can run on the deck?

 

[captaincrunch00]

Yeah, I ran the HP library and tape tools, the drive checks out just fine. It spins at the speed it always does, it writes data the speed it normally does...

The thing is, I cant really change much on this server until after hours tonight if anyone has any good ideas.

 

[gozar]

When this happens to me I can usually use the beutility and run a repair on the database and it clears it up most of the time.

 

[selinathe1]

I'm having a similar problem.
One of the servers is running BE 9.1. I noticed that last night's backup wasn't run. But it seems to have started by looking at Alert tab. In Job Monitor it has the job that was scheduled for last night, still says "scheduled". It's not "On Hold". How could it have a job scheduled for the past date/time?
How do I fix this?


Thx
-selina

 

[captaincrunch00]

Honestly, the only thing I could find to fix it was to stop all the BE services, then restart them all about 2 hours later.

It took 2 hours to stop the services. Even after a reboot.

I think I found out why it wasnt running...