Re: [Veritas-bu] scheduled backups fail to launch

On Thu, Aug 28, 2008 at 1:26 AM, Chad <netbackup-forum AT backupcentral DOT com> wrote:

We have NB 4.5 running on two Linux servers (master and slave).

Around the first of the month, we had to replace the motherboard in the master. Unfortunately the CMOS clock on the new board was set way in the future, far enough that the NTP daemon refused to correct it. The repair dude didn't notice this, and we went through one backup cycle that way.

Since then, the backups on the remote media server do not start as scheduled. If kicked off manually they work just fine.

The only hint I can find is the bpsched log contains messages like this:
log_in_errorDB: skipping backup of client bsd3, policy HD
Q-Stand, schedule 2years because it has exceeded the configured number of tries

I assume somewhere NB mis-remembers it did that backup (in the future).

Where would it keep that information, and how can I reset it.

The quick hack that *might* work would be to shut NetBackup down, rename /usr/openv/netbackup/db/images/$CLIENT/STREAMS to something else, and restart NetBackup. It will then reset the timers for that client - your schedules will start over. Alternatively, you could edit the STREAMS file and put in a timestamp you like - that's even more of a hack and if you break it, you get to keep both pieces.

.../Ed

Ed Wilts, RHCE, BCFP, BCSD, SCSP, SCSE
ewilts AT ewilts DOT org

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu