Great catch Tim, also another reason I've seen with jobs not running and no
errors being reported is when the File System is full, or if the system is
out of resources, semaphores and shared memory segments.  These come into
play if you have been tuning the buffer sizes that NBU uses to write to
tape.

Things to keep in mind.

Bob

-----Original Message-----
From: McMurphy, Tim [mailto:Tim.McMurphy AT cdcgy DOT com]
Sent: Wednesday, October 04, 2000 9:28 AM
To: 'Veritas-bu (E-mail)'
Subject: [Veritas-bu] bpsched phantom daemons


Someone posted asking about scheduled jobs not running and I followed the
thread with interest because we have a similar though not identical problem.


In our case scheduled jobs didn't start and there was no errors in the job
monitor or in the log files. It was intermitent but would happen at least
once or twice a week. It has been driving me nuts for a couple of months.

Diag: We have several classes going at different times to minimize network
congestion. Several times a week one set (incrementals) would finish before
the others would start. The database backup would then run as it was set to
run after any scheduled backup.

What was happening was that there were still phantom bpshced sessions going
after the database backup was finished. I noticed this when I did a
K77netbackup and then ps -ef | grep bp and saw several still running.
Running the bp.kill_all took care of them but I started thinking maybe they
were interfering.

Solution: I switched to manually backing up the database and now 2 weeks
later everything is running fine with zero jobs not run. We are at version
3.2 with the latest patches on all the servers and clients.
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu