Well, this is true if you define "bug" as "something I
don't like".
It's by design, not a bug. The exclude list in
Windows is buried in the registry, that's why bp[gs]etconfig is used for
it. Unix, of course, is file based and all the standard file transfer
methods are viable answers.
Centralized exclude lists would be too broad - unless you
got into some strange naming scheme. If it were on the destination media
server, then every block would have to be backed up and then excluded at the
destination. That'd be too network intrusive.
Policy-based exclude lists might be nice but you'd still
have to have another list on your client for oddball stuff. Certainly the
clients in my standard unix sets are too varied to allow a centralized list on
even a policy level.
There's a couple solutions to this, some of which aren't
very fun but will work.
1. Create a ssh trust relationship to your clients from
your master, use scp pull & push these files.
2. use alternate client bpbackup & bprestore to
transport files
3. bpgp works on earlier versions of NB (this was my old
method)
...ftp, rcp, tftp, all sorts of stuff. It's just
files.
Thanks Mikael,
bpgetconfig do not work on
unix !
I think this is a bug from Netbackup to have
exclude_list file located on the client !
The second bug
is that the bpcoverage do not analyze exclude_list file
!
The solution is may to not use exclude_list file
!
Thanks to all
Didier
Michael Graff Andersen a
écrit :
think a script around bpgetconfig might could supply this
Regards
Michael
2008/5/14, Didier BRUN <didier.brun AT fr.thalesgroup DOT com>:
Hi all,
I search for a solution to centralize all the exclude_list on the
Netbackup Master server.( this is more easy to make periodic checks ... )
Do you know the solution ?
Netbackup 5.1 and 6
Didier
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
