> Exclusion files are client-side only.  If you put one on the
> master server, it doesn't function for the clients.
> 
> Certainly it's something we, the user community, have been
> requesting for a very long time.

Let's not make that a universal "we," okay?  :-)

When I was first thrust into a NetBackup shop in 3.1 days, I, too,
found client-based exclude/include odd, unreasonable and just
annoying.

Until I realized the power and scope of NetBackup compared with the
enterprise backup solutions I was familiar with at that point.  I
could "push" a (or multiple) standard setups if needed, but the part
I still find a beautiful piece of design is that the ultimate
control resides in the owner of the system being backed up.  In
effect:

  Note to all:  by default, your system will be backed up
  in its entirety.  Whatever you don't need backed up [in
  some shops we used chargebacks as incentive] or want to
  keep private [researchers, developers, finance and payroll
  usually loved this part], exclude.  You have the control.

A system owner who _cares_, armed with the exclude/include mechanism
description, is, IMO, the right and proper entity to make these
decisions.  

Client-based exclude/include isn't a lack; it's a feature.


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