Peer Global File Service - Environmental Requirements

NOTE: All Peer Global File Service capabilities are deployed via the Peer Management Center and Peer Agents.

Revision

018

Last Updated

29 June 2020

Server Requirements

Minimum Peer Management Center Server Configuration
  • Windows Server 2012 operating system or later.
  • Must be a dedicated server. Physical servers are preferred and may be necessary in some cases, but high performance VMs running on enterprise-class hypervisors can usually suffice.
  • For customers with Peer Global File Service Basic or Standard licenses:
    • At least 4 processor cores.
    • At least 4GB of system RAM with 2GB dedicated to the main Peer Management Center service and 1GB dedicated to the Broker service.
  • For customers with Peer Global File Service Enterprise licenses:
    • At least 6 processor cores.
    • At least 8GB of system RAM with 4GB dedicated to the main Peer Management Center service and 2GB dedicated to the Broker service.
  • For customers with Peer Global File Service Data Center licenses:
    • At least 8 processor cores.
    • At least 16GB of system RAM with 8GB dedicated to the main Peer Management Center service and 4GB dedicated to the Broker service.
  • At least 100GB of free disk space on a reliable, fast hard drive to accommodate installation and log files. Fast SSD storage is highly recommended to improve performance.
Minimum Agent Server Configuration
  • Windows Server 2012 operating system or later.
  • For enterprise NAS environments, this 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.
  • For customers with Peer Global File Service Basic or Standard licenses:
    • At least 4 processor cores.
    • At least 4GB of system RAM with at least 2GB dedicated to the Agent service.
  • For customers with Peer Global File Service Enterprise licenses:
    • At least 6 processor cores.
    • At least 8GB of system RAM with at least 4GB dedicated to the Agent service.
  • For customers with Peer Global File Service Data Center licenses:
    • At least 8 processor cores.
    • At least 16GB of system RAM with at least 8GB dedicated to the Agent service.
  • At least 50GB of free disk space on a reliable, fast hard drive or RAID array of hard drives to accommodate installation and log files. Fast SSD storage is highly recommended to improve performance.

Additional 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. A Peer Agent must be installed on all participating Windows file servers and CEE/FPolicy/Partner Servers.
  3. All folders to be replicated must either be on the local Windows server (NTFS only) where the Agent is installed, or be hosted on an EMC VNX, EMC Isilon, NetApp 7-Mode, NetApp cDOT, or Nutanix Files enterprise NAS platform.
  4. Windows Failover Cluster environments are supported in running both the Peer Management Center as well as the Peer Agent running attached to a clustered file server role. Windows Failover Clustering is not currently supported for use with enterprise NAS platforms. For more details, please contact your sales representative.
  5. Enterprise NAS platforms require that additional prerequisites be met.
  6. The Peer Agent process (PL-Agent.exe) should be excluded from all anti-malware applications on the Windows server where the Agent is installed.
  7. Short filename support using the 8.3 naming convention MUST be disabled on the storage devices managed by the Peer Agent. 
  8. File-level encryption technologies are NOT currently supported. If file server encryption is required, a volume-level encryption tool that operates transparently (like Microsoft BitLocker) is recommended.
  9. Deduplication technology on Microsoft Windows 2012 and above is supported.
  10. The Peer Agent must be installed as a Windows service, running under a domain account with FULL ACCESS to the folders it will be replicating and locking. The Peer Management Center services can run under a local system account.
  11. No other replication technologies (such as Microsoft DFS-R) should be touching the data that is managed by the Peer Agent.
  12. All Peer Agent servers must have some form of network access to the server where the Peer Management Center is installed. The Agents must be configured with the host name or IP Address of the Peer Management Center server. No firewalls can block traffic on the configured port (which is 61617 by default when using SSL; 61616 by default when not using SSL).
  13. File Collaboration jobs only propagate locks when a file is opened with a read-write lock (for example, using MS Word, MS Excel, etc.). If a file is opened in read-only mode without an exclusive write lock, or if the application closes all handles to the file (for example, Notepad, WordPad, etc.), the lock will not be detected and acted on.
  14. File Collaboration jobs require that all end-user file access and modifications must be done through a network share or mapped drive. Any activity on a participating file server that is generated from the file server itself will not be detected and acted on.
  15. The Peer Management Center and Peer Agent are intended to be installed and maintained by a qualified System Administrator and not a typical end-user.