Retaining audit data - BlueCat Integrity - 9.3.0

Address Manager Administration Guide

Product name
BlueCat Integrity

Starting in Address Manager v9.3.0, the Audit Data Retention setting replaces the former History Archive and Purge and Transaction History Writing settings.

Formerly, BAM administrators could configure a single retention period, and schedule purge themselves. From Address Manager v9.3.0, users can 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:
  1. Administrative History: internal transactions, such as any changes made within the BAM via GUI or API
  2. Session and Event History: logs of session login/logout activities and events
  3. 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
  4. DDNS Transaction History: external transactions, such as changes to the HOST records and their mappings to IP address and DHCIDs
Note: For users upgrading from a previous release of BAM, and had set up either a daily or a monthly purge schedule, the retention settings will be initialized to correspond to the implied retention of that schedule. However, users should review and, if desired, adjust those values after the upgrade to Address Manager v9.3.0.