I had a situation where I needed to change the /usr/openv/netbackup/db/class//includes file directly by using a bash script. Afterwards, when I ran the Netbackup policy the changes that I had made in the file and which also were reflected in the GUI as well did not take place during the actual backup. The old includes file was somehow being used.
How can this be thought? Worse yet I found through trial and error that this was not happening all of the time. Just some of the time. Baffled, I found out it is best to always use the bpplinclude command to make changes to this portion of the Netbackup policy. I found that using the following command to both delete and add the modified includes file will rectify such a situation. Following is such an example and assumes the file being used as the “add” file is actually a file that was previously generated by a script.
/usr/openv/netbackup/bin/admincmd/bpplinclude -delete -f /usr/openv/netbackup/db/class//includes
/usr/openv/netbackup/bin/admincmd/bpplinclude -add -f /home/my_home_dir/