Scheduling and Replication Issues

Documentation replication conflicts can occur on cluster servers if multiple scans are run at the same time on different servers, or a scan is run while a replication event is in progress. A way around this is to ensure that replication occurs between the servers both before and after an on-demand scan, and that only one server is nominated to run the on-demand scans for the clustered databases.

You can reduce the risk of replication conflicts within servers. If you perform on-demand scans on databases that are replicated across multiple servers, only run those scans when the databases have low levels of usage. We recommend that you run an on-demand scan against one replica of the databases, and then replicate the scanned databases throughout the system as soon as the scan has finished.

If an infected document has its form and default form removed, the on-access scan (during database replication) and on-demand scan schedules cannot scan the document as it cannot be opened. This only becomes an issue if the document is provided with a form and then opened when scanning is not being performed.