The StrongKey Tellaro appliance includes a replication module that replicates objects stored in database tables across the cluster. For the KeyAppliance (SAKA) module, this includes all tables in the strongkeylite schema.

While the replication process works efficiently most of the time, some sites may choose to  exclude some table data whose information is also available in the appliance’s log file(s) from the replication process – this reduces resource consumption on very busy machines. These include the DECRYPTION_REQUESTS and SEARCH_REQUESTS tables.

For compliance to regulations mandating audit trails of transactions, there are two mechanisms for recovering information from these two tables (when needed):

1. The server that processed the decryption or the search webservice operation will always have the record within its tables on that cluster-node. A database backup of that cluster-node, stored offline, will enable recovery of data for any audit; and
2. The server that processed the decryption or the search webservice operation will also have transaction information recorded in the server’s log file. If customers are using log-management tools with archival capabilities, the archive records serve as a resource for audit logs.

Customers who choose to take advantage of this efficiency MUST plan to backup either the databases and/or Payara log files of appliances where the configurable property is enabled.