How can I prune the Statseeker Database and/or reduce the backup size?

You can prune the database via the Administration Tool:

1. Administration Tool > Network Discovery - Advanced Options > Advanced Options
2. Click File Edit Mode, located at the bottom of the form
   This will display a list of attribute::value pairs.
3. Scroll to the History section and set values for:
   
   Keep Syslog History For
   Keep Traps History For
   Keep Interface Event History For
   Keep Time Series History For
   Keep Threshold Event History For
   Keep Device Event History For
   
   

A value of 0 means keep the information forever.

I suggest setting the Times Series History to a minimum of 400 days, this is basically a year and a month and allows comparison with the same day last year.  

The pruning action is taken as part of a daily database tuning process which occurs at 00:30 server-time, this process is called nim-db-tune.

Definitions

Keep Syslog History For - sets the retention period for any syslog information Statseeker has been configured to collect.

Keep Traps History For - sets the retention period for any trap information Statseeker has been configured to collect.

Keep Interface Event History For - sets the retention period for interface event data which is when something not normal occurs. This could be interface up/down events.

Keep Time Series History For - set the retention period for time-series data collected  through polling/requests and this data  consists of interface traffic data, ping data, and device stats like temperature, memory, and CPU. This is likely to be the largest consumer of storage space for most customers.  

Keep Threshold Event History For - sets the retention period for threshold event data.

Keep Device Event History For - sets the retention period for interface event data which is when something not normal occurs. This could be interface up/down events.

We keep different histories for the data types because typically, customers don't want to keep events history nearly as long as time-series data.

Also if you are monitoring OperStatus and happen to be collecting it on access switches, the interface event DB can get massive in a hurry so having a timetable just for interface event cleanup is beneficial.

To get an Idea of how much space these DB's are using you can run the command below on the command line:

du -h /home |sort -h

e.g.

7.1G    /home/statseeker/nim/data
7.5G    /home/statseeker/nim
8.5G    /home/statseeker
 29G    /home/system
 37G    /home

You are looking to see how much space the directory /home/statseeker/nim/data is using. This should be the largest directory in /home.

If you would like to check the age of the oldest data block you can run the command below and scroll through the list which has the date information at the end of the line :

nim-ts config list; echo -e "\n\nsnapshots:"; nim-ts dump file

e.g.

1879337233 14:2:1681:1   daily/sched_60_24h/zdata_1m_i4/002/7004691101BF900001BF95FF01010000.z - 1759887360 to 1759979520 - Wed Oct  8 11:36:00 2025 to Thu Oct  9 13:12:00 2025