GFI Archiver's Database Activity Auditing feature uses the tracing capabilities of SQL Server® to record all activities affecting the archive databases. This article provides information about the feature.
Note: The Auditing feature cannot be enabled on Archive Stores based on the GFI Archiver (Firebird) database and file system. We recommend using your OS User Configuration Auditing and User Trail features for this environment.
Trace data is stored in a text file in a user-specified location in the SQL Server® machine. There is one trace file per server containing trace data from all Archive Stores hosted on the server. The SQL Server® service uses an exclusive lock for the trace file to prevent it from getting tampered. From GFI Archiver, you can then trigger the process to upload the trace files into the auditing database. You can view auditing reports through the Auditing Reports page in the console after uploading the trace files.
Important: You can enable the Auditing feature for Archive Stores based on SQL Server® and SQL Server® with the file system. However, if unauthorized access to the server is given, a potential hacker could delete or modify the archived data in the database and prevent the archived data from being audited.
Please read the articles below to learn more about: