Formerly, BAM administrators could configure a single retention period, and schedule
purge themselves. You can now select more granular history retention based on the
audit data type via GUI or API. Administrators don't need to manage or schedule the
purge; instead, it is done automatically to ensure transactions older than the
selected retention are regularly purged to maintain the database size. When data is
purged, space is immediately reclaimed and made available for use by other tables.
This feature ensures that there will be at least as much history retained as
specified in the retention settings.
Note: The data purged from BAM is not archived
and cannot be retrieved.
There are four categories of historical data for which you can specify the retention
period in the BAM database:
- Administrative History: internal transactions, such as any changes made within the BAM via GUI or API
- Session and Event History: logs of session login/logout activities and events
- DHCP Transaction History: external transactions, such as changes to the IP address state and related MAC address and DHCP unique identifier (DUID) as a result of dynamic DHCP activity, including lease history
- DDNS Transaction History: external transactions, such as changes to the HOST records and their mappings to IP address and DHCIDs