Question

Audit Trail 9.2

Audit Trail

Updated June 17, 2015

asked on February 19, 2015

I have noticed a problem with our LF Audit trail since we upgraded to 9.2. We have setup the LF Audit Trail to pull data for the last 181 days. We store the raw audit files in 2 locations. F drive for all rolled over audit files and the current audit file on our G drive which contains the latest audit data. What we are finding is when the file on the G drive fills up and is rolled over to the F drive and starts fresh. The data available to the Audit Trail only shows data up to the point of the latest rolled over audit data on the F drive. So if the g drive file rolled over the audit file to the F drive, only the data up to the point of the latest F drive data is available for view in the LF Audit reporting. The data in the file of the G drive is not available until it is rolled over to the F drive. Even though we said load the data for the latest 181 days.

In essence any audit data contained in the current log file on the G drive (which contains data for the latest 1-3 days until it rolls over) is not being loaded to the database for availability in the Audit Reporting.

I do not see anything showing up in the event viewer where the LF Audit Trail program runs from. Any ideas?

0 0

Replies

replied on February 23, 2015

Normally Audit Trail should be communicating with the Laserfiche server to get the audit data, and it won't matter how the rollover is configured. You would have AT configured to read log files from a folder location if the files had been moved to another location for storage (for example). So double-check the configuration in Audit Trail.

Nothing related to this would have changed in 9.2. I can only guess that the configuration was changed at the same time.

0 0

replied on June 9, 2015

Just upgraded to 9.2. We are having the same issue except all audit files are on the same drive. When running a query it only shows data from rollover files. It does not show data from the active Audit Log file.

I have a support case open but was curious if this got resolved.

Thanks!

0 0

replied on June 17, 2015

Response from Support

SQL Server 2008 R2 or SQL 2012?

I’ve done more digging and found out that there’s a date time design change for SQL 2012.

That’s why Audit Trail doesn’t properly keep track of the current (non-rolled) log.

This issue will be fixed in Audit Trail 10.

0 0

You are not allowed to follow up in this post.

Question

Question

Audit Trail 9.2

Replies

Sign in to reply to this post.