1 of 1 people found this helpful
Suggest looking at the performance tweaks available for reducing strain when updates occur.
The biggest hinderance to your described issue will be the disk I/O required to read the megabytes of signature file data as the scanner reinitializes following the DAT update. It will take longer than 10s for almost any hardware out there.
But, the update performance tweaks also include reducing priority of our scanner threads to "normal", which should allow for the SQL mirroring to get some CPU time.
Thanks wwarren. There were two exclusions that I had left out that were recommended by mcafee. Once I added those exclusions, mirrirong with the witness fucntions fine.