Antivirus exclusions for Storage Replica

Simon Walker 21 Reputation points
2021-07-22T16:11:29.357+00:00

Hi all,

I'm having some issues with Storage Replica not playing nicely with Mcafee ENS on two 2016 servers. They're set up as a failover cluster with a disk on each server set up to replicate using Storage Replica. With the ENS on-access scan disable I can run "Sync-SRGroup -Name $srgroup_name" from PowerShell and the two disks will find each other and quickly say "Continuously replicating" as their status. With the on-access scan enabled if I run Sync-SRGroup the disks will stay on "ConnectingToSource"/"WaitingForDestination" indefinitely. Having spoken to Mcafee support they say that we need to configure additional exclusions for on-access scan however they weren't able to tell me what those exclusions actually were. I've added those recommended in this article: https://learn.microsoft.com/en-GB/troubleshoot/windows-server/high-availability/not-cluster-aware-antivirus-software-cause-issue, (essentially just %Systemroot%\Cluster as the quorum is not on a locally attached disk and we're not using a cluster service account) but this doesn't appear to be enough to get it working.

Has anyone else had similar issues with Storage Replica and antivirus?

Windows Server 2016
Windows Server 2016
A Microsoft server operating system that supports enterprise-level management updated to data storage.
2,370 questions
{count} votes

3 answers

Sort by: Most helpful
  1. YOUNSI, Menad 1 Reputation point
    2021-09-28T08:53:38.537+00:00

    Hi , we are the same problem on my company with mcafee agent the replication stuck to (waiting destination) when we disconnect mcafee agent , the replication pass to "continous replicating".

    SimonWalker-5942 have you find a solution since 2 month ?

    Thanks in advance for your help.


  2. YOUNSI, Menad 1 Reputation point
    2021-11-29T13:20:09.247+00:00

    Hello , I don't know if you have find a solution , but we have solve this problem with Mcafee , it must to put "SYSTEM" on process in low risk on the on access configuration. After that we don't have the "connecting to source/ waiting to destination"


  3. Rodrigo Holanda 1 Reputation point
    2021-11-30T19:30:29.027+00:00

    Any update related to this case? Im facing the issue.

    0 comments No comments