Netbackup 6.5.5 Deleted policy, still attempts to run

[aschirox]

Hope someone has a solution for this.  I deleted a policy, it still attempts to run the backup job.  I found the article https://www-secure.symantec.com/connect/forums/netbackup-continues-submit-and-execute-policy-even-th... . 

Steps taken from article:

1. restart netbackup
2. update nbpem daemon

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

Niether of these steps have worked.  Anyone have a direction to point me in?

Andy

[RamNagalla]

what is the status of the job that is triggering...?

 does it getting successfull?

does this policy is file system backup or for Database backups?

[aschirox]

what is the status of the job that is triggering...?      Status 230

 does it getting successfull?                                   No

does this policy is file system backup or for Database backups?

This is a Standard backup of logs on a linux Apache server.

[RamNagalla · Accepted solution]

status 230  

Message: the specified policy does not exist in the configuration database

there is nothing wrong in netbackup , as the policy is already deleted its just failing with 230

so this indicates that the job is not being triggred by Netbackup. 

some other tool (may be cron or 3rd party scheduler) is triggering this..

so you  need to find out from where this job is being triggering and stop/ remove from that scheduler if you dont what it to run

[aschirox]

So far no entry in cron on either Nbu1 or the server in question.  This policy was created only a month ago and deleted last week.  Their is an identical policy different name and server, same backup selections.  To save on tapes I deleted the policy and added the client to the identical policy.  That policy is running correctly and backing up both clients.  There are no third party schedulers involved.

I've checked /usr/openv/netbackup/db/class, there is no listing for the deleted policy.

[Marianne]

To find out where the backup is generated from: 

Create bprd log folder on the master server and restart NBU.

Next time the backup is attempted, you will see the IP address of where the connection request is coming from in the bprd log.

[RamNagalla]

yes... bprd log is the one that helps to find the source of the request...