Please see this thread https://www-secure.symantec.com/connect/forums/cli...

In this thread I posted a script that leverages exclude list administration.

Well I have note tired this but it seems to me the solution for your query...

 http://seer.entsupport.symantec.com/docs/265896.htm

Please do check this artical

 
http://enterpriseunix.blogspot.com/2007/11/veritas...

You have the option of using NetBackup commands but you won't be able to get away without having to do a bit of scripting or batching.  You can use Excel to make it a bit easier to build the commands for you.  I've done mine automatically but this might just point you in the right direction.

Get a list of all your servers using something like bpplclients -allunique

You can build a list of commands in Excel using bpgetconfig -M <clientname> -X Exclude > <clientname.txt>

This should generate a file for each client with the current Exclude lists for that client

You can use anything to add you global exclusions to each of the files that were extracted earlier <clientname.txt> (e.g. echo "blah blah blah" >> <clientname.txt> if you like)

Now use Excel to build the following command for each server.

bpsetconfig -h <clientname> <clientname.txt>

where clientname.txt matches the name of the extracted file.

Note: You can't just run the bpsetconfig with your new additions as this command replaces the the entire exclude list on the client which is why you need to combine them.

Still a bit of work but possibly a bit more manageable.

Cheers
 

I never thought this would be such a full time job.

My experience is mostly with EMC's Legato, where i can make a server side exclude list, assign it to groups, clients, etc. and they will all follow it.

I think it's a major design flaw to have to update every client when you want to exclude say /var/tmp from all your Solaris machines, or *.mp3 from your users home directories.

Maybe i'm looking at wrong, anyone have any ideas as to why there isn't a global exclude list or a way to add excludes to the enterprise?

Thanks for the answers, looks like my work just doubled (again)

QM

I find the best way is just to highlight all the clients and select properties and make a cup of tea while they all connect!

Then once you have that open you can add exclusions to all the clients at once.

Just another option for you.

I honestly don't know if this feature is still supported.  It's worth a shot.
http://seer.entsupport.symantec.com/docs/182189.htm

You're right, seems like it should be a lot easier for an enterprise-level product.

If you have a Windows based master server...

Logon to the Netbackup Master Server with Admin rights

Open the Backup, Archive, Restore GUI

Go to the File Menu - click Netbackup Client Properties

Click the Exclude List tab

There is a Help button that goes over syntax etc.

check it out as your solution

While i very much like a tiered form of exclusion (I.e. you have a global exclude, then a policy level exclude, and then a client level exclude) that gets combined together at the end, i think the difficulty is saying at which point the "exceptions to exclude list" apply. If a global exclude has an exception to not backup .mdb files but you want mdb backed up on the client, which override gets taken first? I think thats why they kept it down to the client to initiate.

For windows clients i generally do a mass update to their excludes by selecting them all in the clients view (i know it freezes for awhile, it has to see if it can communicate and get version, etc.) but while im doing other work, i can come back to it and edit it then.

You should recommend it as an idea, just make sure to give examples of how the developers could handle the situation similar to my issue above. Ideas are great until it affects you in a way you didnt plan.

I am using that way to do add common exclusions;