Here's the summary to my problem, as found by Veritas support.
Upon completion of a backup, NetBackup schedules an examination of images
for expiry. This takes a while, particularly if some of your NetBackup
clients are offline at the time as was the case here.
Solution is to touch file /usr/openv/netbackup/bin/NOexpire which forces
the system not to try expiring images. Later on, when you've got plenty of
"slack" time, like outside your backup window, remove the NOexpire file, run
a small backup which will then run the expiry stuff.
On Wed, 22 Apr 1998 email@example.com wrote:
> Recently moved our NetBackup 3.0 master server from a Sparc 20 running Solaris
> 2.4 onto an Ultra 1. with a fresh install of Solaris 2.5.1 on there, complete
> with recommended patches etc.
> Moved /usr/openv straight onto the new machine and mounted it ok. Updated
> /etc/services, /etc/inetd.conf, /etc/system (extra semaphores/messages etc),
> replaced Solaris 2.4 executables for NetBackup client with the Solaris 2.5
> The problem is that a backup can be run okay, but it leaves the "bpsched
> -mainempty" job still there, resulting in NetBackup being unable to
> schedule any more jobs until this turkey is killed.
> If you have any ideas, please drop me a line. I'll summarize.
> Steve Kay
> 17:02:56  <4> bpsched: INITIATING...
> 17:02:56  <2> logparams: /usr/openv/netbackup/bin/bpsched -mainempty
> 17:02:56  <4> main_bpsched: another bpsched is already main-sched
> 17:02:58  <4> write_worklists_to_file: writing work to /usr/openv/netbackup/bin/bpsched.d/worklist.776
> 17:02:59  <4> main_bpsched: another bpsched is already main-sched
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:12:38 CDT