03-23-2017 02:35 AM
Hi experts,
I have de-activated a policy in NetBackup, but it is still running. I have deleted it but no way.
What can I do to stop the policy from running while it is de-activated.
I have done the folloing but didn't solve the issue:
1. Stop NetBackup Services on the master server
2. Remove the following files and directories from the master server
/usr/openv/netbackup/bin/bpsched.d/*
/usr/openv/netbackup/bin/bprd.d/*
/usr/openv/netbackup/db/jobs/pempersist2
/usr/openv/netbackup/db/jobs/restart/*
3. Start NetBackup Services
4. Run the command below to force nbpem to re-read configurations and rebuild its cache instead of waiting the default time to do so:
/usr/openv/netbackup/bin/admincmd/nbpemreq -updatepolicies
Thanks
03-30-2017 03:22 AM
Also nothing intreresting inside bprd logs activated yesterday
root@Backup # cd /opt/openv/netbackup/logs/bprd/
root@Backup # ls -ltr
total 2
-rw-r--r-- 1 root root 327 Mar 30 00:00 root.033017_00001.log
root@Backup # cat root.033017_00001.log
00:00:05.746 [20457.1] <2> bprd: new open file limit cur = 1024 max = 65536
00:00:05.747 [20457.1] <2> SetMaxDataLimit: maximum data size: current=-3 max=-3
00:00:05.747 [20457.1] <4> bprd: VERBOSE changing from 0 to 5
00:00:05.747 [20457.1] <2> bprd: Recycle request from masterserverBZ ignored - it is not the master server.
03-30-2017 10:16 PM
Hello
Moving policy folder from one location to another may corrupt the policy.
Better to take policy detail using command and refer it to recreate in future.
Location:/usr/openv/netbackup/bin/admincmd/
#bppllist <Policy_Name> -U > /tmp/<Policy_Name>1.txt
Displays a full (long) listing.
#bppllist <Policy_Name> -L > /tmp/<Policy_Name>2.txt
Bring down the NBU services on Master server and remove the policy folder.
The database backup is client site backup. We are removing all references regarding that client.
-Deleting policy from NBU and folder from path will remove all references for auto schedule.
-Renamed script will not get execute and not send any request to master server
After doing this still facing problem then 100% request is coming from different server which having same detail
Or
You have multiple scripts configured and running by user or cron job.
Thanks & Regards
04-03-2017 01:33 AM
Hi Tousif,
The solution seems working. The policy doesn't execute again. Is it possible to create the policy again and de-activate it. Are we sure the issue won't appear again. We need this policy in the future.
Thanks