Video Screencast Help

Netbackup continues to submit and execute policy even though policy has been deleted.

Created: 20 Aug 2009 • Updated: 21 May 2010 | 9 comments

Wondering if anyone has ever seen this.  I created several backup policies on our 6.5.2 master and set up run times within the policies. Once they were no longer required, I deleted all the policies but that night, they all executed at the same scheduled time. I waited another night and again they executed at the scheduled time. The next morning, I recycled the Netbackup services on the master and the policies are no longer executing now. I've done this hundreds of times in the past and once the policy has been deleted, it has never executed again. A services recycle has never been required in the past.  Any ideas? 

Comments 9 CommentsJump to latest comment

Mouse's picture

Never seen it, but if it still sits in the 6.5.4, I fear for our customers, some of them add/delete policy every day....

rj_nbu's picture

netbackup's scheduler (nbpem) creates a worklist of jobs that are due to run . If you delete a policy, netbackup doesn't automatically remove that policy from its worklist. You have 2 ways to let netbackup scheduler know that something has changed:

1. restart netbackup
2. update nbpem daemon

/usr/openv/netbackup/bin/admincmd/nbpemreq -updatepolicies

-Rajeev
"Unix IS user friendly... It's just selective about who its friends are"

Mouse's picture

Thanks Rajeev, but can you please explain one more thing for me: If scheduler process "wakes up" every 10 minutes (maybe with another frequency, doesn't matter), doesn't it update worklist themselves?

rj_nbu's picture

Thats how it is supposed to work :)    6.5.2 had an issue in nbpem where the worklist would not get updated, thus you had to either restart nbu or manually update using nbpemreq

-Rajeev
"Unix IS user friendly... It's just selective about who its friends are"

Android's picture

NBU should check for updtes to policies every ten minutes by default you can change this value.  See my popst below.

Android's picture

I had a customer who experiencing this same behavior.  A call was opened with Symantec and the cause was never found.  However after upgrading to 6.5.4 the problem did go away. 

There were a lot of issues with nbpem, some related to pempersist file for all version of 6.5. Sometimes scheduled jobs would not run. Most were dealt with in the release of 6.5.3.1.  I would seriously consider upgrading, not only to deal with your current issue but to avoid others related to nbpem. 

fredym's picture

Thanks Rajiv. I'll pass the info to everyone.   We're looking at upgrading shortly sp hopefully the problems will disappear.