> You know, I've been scratching my head over this one too
> but I can't remember what the logic was or where I got the
> info from (or even when).  Whatever it was, it made sense
> to me at the time...
> 
> I had a case open with support and I threw this question
> out and I got the following recommendation (though no
> technote to back it up):
> 
> Exclude from regular backups on the master:
> 
> /usr/openv/db/data
> /usr/openv/netbackup/db
> 
> The backup selection in a catalog backup has the following paths:
> 
> /usr/openv/netbackup/db
> /usr/openv/var/
> Relational Database path  (/usr/openv/db/data)

Neil, I think we're talking about two different things.  The
recommendation above is "don't back up the relational (db/data) or
flat-file (netbackup/db) databases with a regular filesystem backup
of the master--there's no point since the relational will be
inconsistent and a normal restore can restore any of the flat
files--which wasn't the case with the cold-catalog-backup format.

What I'm talking about below is the original poster excluding any
paths from a _hot_ catalog backup:  

>> Directories to exclude from hot catalog backup policy (6.0
>> master)
>>
>> /usr/openv/netbackup/db/images/<master>

I can't think of any reason to do that.  Well, none that aren't
_really_ convoluted.  And I don't know of a way to alter the
selection list of the NBU_Catalog policy type--though you could use
an exclude_list to accomplish that.

Skipping the imageDB in a _cold_ catalog backup used to be the norm
when your imageDB got too big to back up in the available time, or
when the catalog backup wouldn't fit on one tape.  The manual
documents the two-phase [cold] catalog backup setup for those
situations.  But a hot runs concurrently with other backups, can
span tapes and can do incrementals so there should be no need to
"improve" the hot catalog backup by excluding things from it.

> On 1/23/10 1:28 PM, "bob944" <bob944 AT attglobal DOT net> wrote:
> 
> >> Directories to exclude from hot catalog backup policy (6.0
> master)
> >>
> >> /usr/openv/netbackup/db/images/<master>
> >
> > Curious about why one would want to do that in a hot catalog
> backup.
> > Is that a recommendation in a manual that I've missed?  (Just
> > checked my 6.0 Admin I and II and didn't see it.)
> >
> > Is it possible you have that as a legacy of a two-phase cold
> catalog
> > backup implementation?
> >
> > Personally, I don't exclude _anything_ from the NBU-Catalog
> > policy--including being careful not to have a general
> exclude_list
> > on the master.


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