How to update the "nbpem" daemon after making changes to a policy without waiting for the Policy Update Interval to take effect

 

The Veritas NetBackup (tm) 6.0 System Administrator's Guide describes a new global attribute called Policy Update Interval.  This controls how often the NetBackup Policy Execution Manager (nbpem) daemon will check for new policies or for updates to existing policies.  By default, the value is 10 minutes. This means that new policies or changes to existing policies will not go active immediately.  The nbpemreq command can be used in situations where a change to a policy needs to take effect immediately.

To submit changes to a policy immediately,  run the following command:
# cd /usr/openv/netbackup/bin/admincmd
# ./nbpemreq -updatepolicies

This will cause the nbpem daemon to update with any changes to policies.  A policy that has an open backup window and is scheduled to run will appear in the Activity Monitor.

Unified logging will show entries every ten minutes for JobScheduler::doPolicyChanges.  These messages will appear at a logging level of 5 for nbpem.  Anytime a policy is modified,  additional log messages will appear listing what policy has been updated.  These messages will be logged at a logging level of 2 for nbpem.

To list all policy changes that have occurred over the last twelve hours,  run the command:
# vxlogview -p 51216 -o 116 --who 'doPolicyChanges' -t 12:00:00 -d all

The following messages show a normal check for policy updates that detected no changes.

11/11/05 10:30:57.495 [Debug] NB 51216 nbpem 116 PID:5844 TID:1 [No context] 5 [JobScheduler::doPolicyChanges] +++ ENTERING +++ : obj = ffbff120 (JobScheduler.cpp:5013)

11/11/05 10:30:57.495 [Debug] NB 51216 nbpem 116 PID:5844 TID:1 [No context] 5 [JobScheduler::doPolicyChanges] --- EXITING --- : obj = ffbff120 (JobScheduler.cpp:5013)

The following messages show a normal check for policy updates that occurred ten minutes later.  This check detected one policy in need of updating.

11/11/05 10:40:57.458 [Debug] NB 51216 nbpem 116 PID:5844 TID:1 [No context] 5 [JobScheduler::doPolicyChanges] +++ ENTERING +++ : obj = ffbff120 (JobScheduler.cpp:5013)

11/11/05 10:40:57.459 [Debug] NB 51216 nbpem 116 PID:5844 TID:1 [No context] 2 [JobScheduler::doPolicyChanges] updating policy test-policy(JobScheduler.cpp:5024)

11/11/05 10:40:58.100 [Debug] NB 51216 nbpem 116 PID:5844 TID:1 [No context] 5 [JobScheduler::doPolicyChanges] --- EXITING --- : obj = ffbff120 (JobScheduler.cpp:5013)

The following messages were logged by running the nbpemreq command to update policies immediately.  This detected two policies in need of updating.

11/11/05 10:41:56.560 [Debug] NB 51216 nbpem 116 PID:5844 TID:9 [No context] 5 [JobScheduler::doPolicyChanges] +++ ENTERING +++ : obj = ffbff120 (JobScheduler.cpp:5013)

11/11/05 10:41:56.560 [Debug] NB 51216 nbpem 116 PID:5844 TID:9 [No context] 2 [JobScheduler::doPolicyChanges] updating policy __DSSU_POLICY_disk-stu1(JobScheduler.cpp:5024)

11/11/05 10:41:56.648 [Debug] NB 51216 nbpem 116 PID:5844 TID:9 [No context] 2 [JobScheduler::doPolicyChanges] updating policy __DSSU_POLICY_disk-stu0(JobScheduler.cpp:5024)

11/11/05 10:41:56.717 [Debug] NB 51216 nbpem 116 PID:5844 TID:9 [No context] 5 [JobScheduler::doPolicyChanges] --- EXITING --- : obj = ffbff120 (JobScheduler.cpp:5013)

 

The logs can be searched for these entries to verify that a change to a policy has been registered with NetBackup 6.0.