Veritas-bu

[Veritas-bu] Sporadic, if not erratic NB database backups

2001-12-21 13:24:51
Subject: [Veritas-bu] Sporadic, if not erratic NB database backups
From: PWinkeler AT officemax DOT com (Winkeler, Paul)
Date: Fri, 21 Dec 2001 13:24:51 -0500
Greg

That sounds like it might be the cause of the problem;  Our backup schedule
is pretty much active 24 hours a day, 7 days a week.  At night we run the
usual plethora of system backups but in the wee hours of the morning we
split off a mirror of a 2.5Tb database and its backup takes the better part
of the day (mixed with steady stream of Oracle archive logs) until the whole
process repeats itself come evening time.
To eliminate further confusion as to how the NB database backup is
configured, here is the output of bpsyncinfo:
--------------------------------------------------------------
Frequency of DB Backup:  after each successful backup schedule

  Server: bkupsrv1.bkup
  Sequence # 1    Last Media Used: S00413

     Written            Allocated          Type   Density  Media
     -----------------  -----------------  ----   -------  -----
  1  12/09/01 12:59:07  02/12/01 10:28:28  RMedia dlt      S00413
  2  12/06/01 12:36:07  12/04/01 17:19:18  RMedia dlt      S03640

  Paths Included:
    opscenter.bkup:/usr/openv/netbackup/db
    opscenter.bkup:/usr/openv/volmgr/database
    bkupsrv1.bkup:/usr/openv/netbackup/db
    bkupsrv1.bkup:/usr/openv/volmgr/database
    bkupsrv2.bkup:/usr/openv/netbackup/db
    bkupsrv2.bkup:/usr/openv/volmgr/database
--------------------------------------------------------------
The DBBACKUP_CALLED log file has these last few lines:
--------------------------------------------------------------
Sun Dec 9 13:29:31 EST 2001 NetBackup databases backed up on TAPE S00413
Sun Dec 9 13:37:31 EST 2001 NetBackup database backup FAILED to TAPE S03640
Mon Dec 10 23:01:37 EST 2001 NetBackup database backup FAILED to TAPE S03640
Mon Dec 10 23:03:17 EST 2001 NetBackup database backup FAILED to TAPE S03640
Tue Dec 11 18:43:14 EST 2001 NetBackup database backup FAILED to TAPE S03640
--------------------------------------------------------------
indicating that there haven't even been attempts to do a backup since last
December 11th!

-----Original Message-----
From: Greg Nelson [mailto:greg.nelson AT veritas DOT com]
Sent: Friday, December 21, 2001 12:57 PM
To: 'Winkeler, Paul'
Subject: RE: [Veritas-bu] Sporadic, if not erratic NB database backups


Paul

Make sure you don't have any ACTIVE backups that are hanging around for
days.  If a scheduled backup completes but others are running then the
catalog backup will not take place.  The catalog backup will only run when
the NBU environment is inactive.

-----Original Message-----
From: Winkeler, Paul [mailto:PWinkeler AT officemax DOT com]
Sent: Friday, December 21, 2001 11:36 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Sporadic, if not erratic NB database backups


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.
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu