Exclude and include list for Windows clients are held in registry keys and can be managed from the Master Server/administration GUI via Host Properties > Clients > Windows Client >Exclude Lists tab. Prior to NetBackup 6.5.3, there is no equivalent way to manage UNIX and Linux exclude and include lists. These are held in files that reside in the /usr/openv/netbackupdirectory on each client and can only be created and modified by logging on to the client and editing the files in place.
With the introduction of NetBackup 6.5.3, it is now possible to maintain and manage these files on the Master Server by using the bpgetconfig and bpsetconfig commands to gather the exclude list files from the clients and put them back on the clients after modification.
The qualifiers -i (for include list) and -e (for exclude list) have been added to both commands and are used in the following way:
bpgetconfig -e <filename> <client> [<policy> [<schedule>]]
Retrieves the exclude list file exclude_list from the client <client> and writes it to the location specified by <filename> (the additional qualifiers <policy> and <schedule> allow the files exclude_list.<policy> and exclude_list.<policy>.<schedule> to be retrieved).
bpgetconfig -i <filename> <server> [<policy> [<schedule>]]
Retrieves the include list file include_list from the client <server> and writes it to the location specified by <filename> (the additional qualifiers <policy> and <schedule> allow the files include_list.<policy> and include_list.<policy>.<schedule> to be retrieved).
bpsetconfig -e <filename> -h <client> [-c <policy> [-s <schedule>]]
Writes the file <filename> to /usr/openv/netbackup/exclude_list on the client <client> (the additional qualifiers <policy> and <schedule> allow the files exclude_list.<policy> and exclude_list.<policy>.<schedule> to be written to the client).
bpsetconfig -i <filename> -h <client> [-c <policy> [-s <schedule>]]
Writes the file <filename> to /usr/openv/netbackup/include_list on the client <client> (the additional qualifiers <policy> and <schedule> allow the files include_list.<policy> and include_list.<policy>.<schedule> to be written to the client).
Note that there is no CLI function to list the exclude and include lists present on each client, so a record should be maintained of these. One simple way to do this would be to include the client name in <filename> on the Master Server.
Examples:
1. In the following example, the file exclude_list is retrieved from the client sun01 and written to sun01_exclude_list in the directory/usr/openv/netbackup/lists.
# bpgetconfig -e /usr/openv/netbackup/lists/sun01_exclude_list sun01
2. In the following example, the file /usr/openv/netbackup/lists/sun01_exclude_list.fullbck is written to/usr/openv/netbackup/exclude_list.fullbck on the client sun01.
# bpsetconfig -e /usr/openv/netbackup/lists/sun01_exclude_list.fullbck -h sun01 -c fullbck
