Skip to main content
Skip table of contents

PeerSync - Environmental Requirements

Last Updated05 June 2024

Server Requirements

Minimum PeerSync Configuration for Windows

  • Windows Server 2016 operating system or later.
  • Physical servers are preferred and may be necessary in some cases, but high performance VMs running on enterprise-class hypervisors can usually suffice.
  • Four or more processor cores.
  • At least 4GB of system RAM with 2GB dedicated to PeerSync.
    • We strongly recommend 8GB of system RAM with 4GB dedicated to PeerSync.
  • At least 10GB of free disk space on a reliable hard drive to accommodate installation and log files.

Minimum PeerSync Configuration for Dell EMC, NetApp, and Nutanix Environments

  • Windows Server 2016 operating system or later.
  • Must be a dedicated server without any other CEE, File Activity Monitoring, FPolicy, VSCAN, or similar application running on it.  Physical servers are recommended but not required.
  • Four or more processor cores.
  • At least 4GB of system RAM, with at least 2GB dedicated to PeerSync.
    • We strongly recommend 8GB of system RAM with 4GB dedicated to PeerSync.
  • At least 20GB of free disk space on a reliable, fast hard drive or RAID array of hard drives to accommodate installation and log files.

Minimum PSListener Configuration

  • Windows Server 2016 operating system or later.
  • Physical servers are preferred and may be necessary in some cases, but high performance VMs running on enterprise-class hypervisors can usually suffice.
  • At least two processor cores. Four or more cores are preferred.
  • At least 4GB of system RAM with 2GB dedicated to the PSListener.
    • We recommend 8GB of system RAM with 4GB dedicated to the PSListener.
  • At least 5GB of free disk space on a reliable, fast hard drive or RAID array of hard drives to accommodate installation and log files.

Storage Platform Prerequisites

Enterprise NAS platforms require that additional prerequisites be met.  Please review the prerequisites for your platform(s):

General Requirements and Notes

  1. Required and recommended CPU, memory, and disk space numbers above will vary depending on the size and scope of the environment. These numbers are to be used as a starting point.
  2. It is recommended that PeerSync be run as a service, under a domain account with FULL ACCESS to the folders it will be replicating from and to. If this domain account does not have FULL ACCESS, it must be a local administrator on all storage devices that PeerSync is replicating from and to.
  3. All targets must have the available disk space to cover the size of their corresponding sources, plus additional space to accommodate potential deletions, revisions, and temp files.
  4. The following services MUST be excluded from all anti-malware applications:
    • The PeerSync (PeerSync.exe) and FastSync (FastSync.exe) processes MUST be excluded from all anti-malware applications on the Windows server where PeerSync is installed.
    • The Listener process (PSListener.exe) MUST be excluded from all anti-malware applications on the Windows server where the Listener is installed.
    • If Dell EMC storage devices are being used with the Common Event Enabler, RabbitMQ (erlsrv.exe and epmd.exe), Erlang (erl.exe), Dell EMC Checker Server (CAVA.exe), and Dell EMC CEE Monitor (CEEMtrSvc.exe) MUST also be excluded from all anti-malware applications.

CIFS/SMB Requirements and Notes

  1. Real-time: Real-time change detection in PeerSync for CIFS/SMB is only supported on the local Windows server where PeerSync is installed (NTFS only), or when connecting to either a NetApp FAS device operating in 7-Mode, a NetApp cDOT Storage Virtual Machine, an EMC Celerra/VNX Datamover, a Dell EMC Unity NAS Server, or a Dell EMC Isilon cluster. Real-time change detection is not supported with any other NAS devices.         
  2. Scans: On-demand and scheduled scans are supported for all CIFS/SMB shares, assuming PeerSync has the appropriate access to these shares and the files and folders within them.              


JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.