Odd Status Code 230
Netbackup 220.127.116.11 Windows 2008r2
I have recently started seeing some odd backup failures with status code 230 telling me the specified policy does not exist in the configuration database. In the activity monitor, the failure shows the policy name as *NULL*, and shows the schedule as *NULL* as well. What is so odd is that the client that is failing (GISO101L) is a client that no longer exists. It was repurposed and renamed many months ago to ORAO101L. I've checked in all of my policies and throughout the organization to see if GISO101L still somehow exists anywhere, and it does not. But, it appears that NetBackup thinks it does. The only thing I found that looked promising so far and have tried was removing the pempersist2 file, and letting it recreate, but I'm still seeing the failure. Anyone seen this type of behavior before?