That's correct.  Also, only the most specific exclude_list* is used.

You actually don't need to include /proc and /cdrom, but if you do
include them you may need to change at least /proc to /proc/* (so the
"mount" point gets backed up) so you don't have to recreate it by hand
if you restore the system disk (I've heard Solaris doesn't like to
boot nicely w/o /proc).

Robert L. Harris writes:
> 
> 
> I have 2 oracle database boxes.  Both have an exclude file that
> contains:
> /proc
> /tmp
> core
> /u*/oradata
> /e*/oradata
> /cdrom
> 
> 
> On one machine it's named "/usr/openv/netbackup/exclude_list" and on the
> other it's named "/usr/openv/netbackup/exclude_list.Solaris-prod".  Is
> the extension on the second automatically recognized IF that class runs
> the backup, while if another class runs it, it is ignored?  There is
> only 1 class running against the actual "machine" which is named
> differently.  The Solaris-prod class was from a previous server this was
> migrated from.
> 
> If I move the second file to "exclude_list" do I need to make any
> additional changes?   grepping for exclude in netbackup recursively
> didn't find any config file options.
> 
> 
> :wq!
> ---------------------------------------------------------------------------
> Robert L. Harris                |  Micros~1 :  
> Senior System Engineer          |    For when quality, reliability 
>   at RnD Consulting             |      and security just aren't
>                                 \_       that important!
> DISCLAIMER:
>       These are MY OPINIONS ALONE.  I speak for no-one else.
> FYI:
>  perl -e 'print $i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10);'
> 
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

-- 
Larry Kingery 
                         This space for rent