Hi,

Either there is a bug or something I don't understand, apologies if it's the latter!

We're planning an upgrade from v3.4.14 to v4 and in anticipation of a large and slow data upgrade (85GB DB) we've reduced the history period to 1d in Administration > Housekeeping.  Typical values are 1w to 2w.

As data sizes didn't reduce significantly, we're looked in the DB and found very old data which hasn't been removed by the housekeeper (which we've confirmed is running in the log and also run manually).

Current settings: 

Events and alerts
Enable internal housekeeping YES

Trigger data storage period 90d
Internal data storage period 30d
Network discovery data storage period 7d
Auto-registration data storage period 7d

Services
Enable internal housekeeping YES
Data storage period 7d

Audit
Enable internal housekeeping YES
Data storage period 7d

User sessions
Enable internal housekeeping YES
Data storage period 7d

History
Enable internal housekeeping YES
Override item history period YES
Data storage period 1d

Trends
Enable internal housekeeping YES
Override item trend period YES
Data storage period 365d

Data which we see in the DB is as follows:

• events: 2017-09-27
• history: 2018-09-14
• history_text: 2016-07-11
• history_uint: 2014-10-14
• trends: 2014-10-08
• trends_uint: 2014-10-08
• Data sizes and row counts:

Thanks!