On any given day we typically run upwards of 450 jobs through the scheduler;
In spite of what we feel are high failure rates (roughly one every other
day), the majority of the runs go through without a hitch.  The
configuration tool states my NB database backup schedule options are:
        1) Never (i.e. manual)
        2) After each succesfull schedule
        3) After each succesfull archive
We currently use option 2.  But I am not seeing any NB backup activity for
weeks on end!  How can this be?  What constitutes a successful schedule?

-----Original Message-----
From: Larry Kingery [mailto:larry.kingery AT veritas DOT com]
Sent: Friday, December 21, 2001 12:16 PM
To: Winkeler, Paul
Cc: veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] Sporadic, if not erratic NB database backups


A successful backup session means that at least one of the backups
which ran was successful.  A single backup failure does not cause the
NBU database to not get backed up.

If all backups fail, the NBU db backup doesn't execute, which makes
sense since there's effectively no new info in the db.

Winkeler, Paul writes:
> 
> We are set up to backup the NB database upon successful completion of the
> backup schedule.  Could it truly be the roughly one media error a day that
> causes us to barely do one NB database backup every week?
> 
> If so, what *should* we set the NB backup schedule to?
> 
> Getting even more nervous,
>  Paul Winkeler
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

-- 
Larry Kingery 
                     Of couse, I could be wrong.