ImageCleanup Not Running on Catalog Backups Causing Error 129
Hello,
We are having an issue with our Catalog Backups that I am hoping somebody can shed some light into.
When the disk usage of our catalog backups reach the high-water mark, it is my understanding that an ImageCleanup automatically runs that brings the disk usage back to the low-water mark.
We are using ~13GB/day for the catalog backup. The available storage is 100GB.
Our high-water mark is currently set to 90%, and the low-water mark is set to 60%. Our retention time is set to 4 days.
However, once the disk usage for our catalog passes the 90% mark, an imageCleanup is not running; therefore, once the storage is full, the backup fails with error code 129. We then have to manually remove the images at the Unix level.
Could you be hitting this issue?
NetBackup backup images on disk have reached the expiration date but do not expire. Catalog backup is failing with Status Code 129.
http://symantec.com/docs/TECH163385Resolution is to find the rogue bpdbm cleanup process and kill it - stop NetBackup, make sure there aren't any bpdbms hanging around, then restart NetBackup and manually start a cleanup:
# bpimage -cleanup -allclients