By default Netwrix Auditor databases are using Simple Recovery Model. This is intended for optimal performance and efficient SQL Server resources usage, specifically to minimize the size of the transaction log.
However, you may notice occasionally that the Recovery Model of some Netwrix Auditor’s databases switches to Bulk-Logged and then reverts back to Simple. This happens during the State-in-Time Snapshots upload.
Using the Bulk-Logged Recovery model ensures data consistency when uploading big chunks of data, like State-in-Time snapshots. This behavior is a part of normal product workflow and cannot be changed.
My backup software does not handle revolving recovery models well. Is there are way to keep them static?
Netwrix Auditor stores a copy of all collected data in the Long-Term Archive from which it can be easily imported to a dedicated database. That said, there is no need to back up Netwrix databases; it is recommended to exclude them from the scope of your backup software. If backup is absolutely needed, it is recommended to use native SQL Server backup functionality instead of backing up .mdf and .ldf files via the file system.
If this is not an option, the only solution would be disabling State-in-Time feature for the Monitoring Plans that use the corresponding databases.