PAM Database Scheduler Not Deleting Local Files

Products

• CA Privileged Access Manager (PAM)

Issue/Introduction

The database scheduler has been configured to only keep two backups locally on the PAM appliance.

However, more than two database backups exist on the appliance after the scheduler has been running.

Cause

The Maximum Files To Keep Locally setting is not in effect if the PAM appliance is not configured to send backups to a remote storage.

Resolution

To manually clean up database backup files on the appliance, select them in the UI and click the Delete button.

To have the database scheduler automatically delete the backups, use the Schedule a Backup of the Database documentation page to configure PAM to send the database backups to a remote storage, then enable the "Delete After Successful Send" option and set the number of files for the "Maximum Files To Keep Locally" setting.

Additional Information

The database scheduler will only clean up older database backup files created by the scheduler. These files are called "gkscheddb<datetime>_<version>.gz" and "gkschedcfg<datetime>_<version>.cfg".

Any database backups manually created by the Save Database and Configuration (called "gkdatabase<datetime>.gz" and "gk<datetime>.cfg") or created as part of an upgrade (called "gkdatabase-preupgrade<datetime>.gz") need to be manually deleted regardless of the database scheduler configuration.