Backup image expiration cannot be modified because its SLP processing is not yet complete
- 6 years ago
We do root cause when a need for a SQL script comes up. Sometimes we're able to change the product so that either the situation won't arise, or NetBackup will be able to handle it.
With that in mind, I started searching our recent escalations for such a situation as yours. I found one that seems to match. (ET 3940173, Operation not successful: status = 220 (database system error))
Rather than a SQL script, this one gave a command option that worked for the customer. Try this:
>bpexpdate -backupid xxxxxxxxxxx -d 0 -force_not_complete
The report says that -force_not_complete allows expiration of incomplete SLP images.
BTW, status 220 doesn't always mean something not found - that's status 227. Often when a browse or bplist fails, NetBackup changes the 227 to 220.