Auditing on a synchronized PI Data Archive server

If auditing is enabled for PI MDB, then the Data Archive server continues to generate audit records for PI MDB after migration. This means that changes users make directly in PI MDB are recorded in the Audit Database on the Data Archive server and Audit Viewer can read these changes.

However, Audit Viewer cannot read changes that users make to synchronized content in PI AF. PI AF generates its own audit records for all changes to assets. When you make changes in AF, these changes are recorded on the PI AF server.

Essentially, this means that you have two separate audit trails for the same content: one that keeps track of changes made directly on the PI AF server and one that keeps track of changes made directly on the Data Archive server.