Database maintenance

The settings under the Database Maintenance section of the data processing configuration page control if and how often the system purges the different types of endpoint data it collects. These can be used to automatically purge unused data from the system at regular intervals.

By default, most of the values will be set to 0, which means all endpoint data of those types will be retained by the system indefinitely.

The following table lists all of the settings under the Database Maintenance section:

Setting	Description	Unit	Default
Endpoint Timeout	Amount of time before an inactive endpoint is flagged as retired and removed from primary endpoint views (endpoint data will be purged, but historical data will be retained for the configured historical limit)	Days	0
Endpoint Removal	Amount of time before a retired endpoint and any retained data associated with it are permanently purged from the database	Days	0
Port Timeout	Amount of time before an endpoint whose location (switch/port) has not been updated has its location data removed	Hours	0
ARP Timeout	Amount of time before an endpoint whose IP-to-MAC has not been refreshed via any of Plixer Endpoint Analytics’ collection mechanisms has its IP-to-MAC mapping data cleared from the database	Hours	0
Wireless Timeout	Amount of time before data for an endpoint that was discovered through a wireless access point will be retained without any updates to that data	Hours	0
Historical Limit	Amount of time that the system stores historical endpoint data (MAC history by port/IP/profile) for MAC-discovered endpoints, regardless of the endpoint’s current state (active or retired)	Days	30
Event History	Amount of time that the system retains historical event data for an endpoint in the database	Months	12
Custom Data Auto Removal	When toggled on, custom data objects are automatically deleted when the associated endpoint is removed from the system	N/A	Off