Bug #16214
closed
Maximum Backup Limit Setting Not Enforced
0%
Description
Issue Description:
The value set under Diagnostics > Configuration History > Configuration Backup Settings > Maximum Backups is not being enforced after changing it from the default. Despite specifying a new maximum value, the number of configuration backup files continues to grow beyond the defined limit.
Steps to Reproduce:
1. Navigate to Diagnostics > Configuration History.
2. Under Configuration Backup Settings, change Maximum Backups to a new value (e.g., 32).
3. Apply the changes.
4. Begin creating new aliases.
5. After several aliases have been added, run the following command to count the backup files:
find /conf/backup -type f | wc -l
You'll notice that the number of backup files will exceed the defined limit.
Related issues
Updated by Robert Jacobson 4 months ago
It appears that the cleanup only occurs when the web UI for the configuration history is loaded. On my system, the backups directory grew very large because I had assumed they would be cleaned up automatically -- but they were only cleaned up when I attempted to open the web UI for the configuration history. In fact, the cleanup UI page hung for a very long time, until I eventually got a 502 error. When I reloaded the browser, the extra files had been cleaned up.
Updated by Marcos M 4 months ago
- Is duplicate of Bug #15994: Backup configuration cache is not cleaned automatically added