Print

PeerLock

PeerLink	  	  	     	 Overview Specification Screen Shot Trial Download    PeerLink File Collaboration is an enterprise-level, real-time, multi-directional, distributed file locking and synchronization technology that ensures the same data exists on all participating servers regardless of where changes occur, and prevents users from accessing files that are currently in-use by another user in the session.   A file collaboration session consists of two or more participating servers, and a folder hierarchy called the Watch Set, located on each server which will be kept synchronized by propagating file locks and modifications to all participating servers in real-time.   PeerLink has local and remote characteristics that form the basis of a distributed application framework.PeerLink installations are composed of 3 primary components:   1. PeerLink Hub The Hub is the central component of the PeerLink framework. All PeerLink solutions are installed, configured and started at the Hub.  2. PeerLink Broker The Broker makes up the central messaging system that supports PeerLink applications. The Broker provides the core communication facility that connects the Hub and Agents in a PeerLink collaboration environment.  3. PeerLink Agent The Agent is a lightweight component that is installed on a networked host that enables it to participate in a PeerLink collaboration environment. Image

File Locking for Microsoft DFSR

(The missing feature)

Effective file sharing and collaboration environments require the combination of file replication and locking. Without file locking, users will eventually encounter corrupted files and version conflicts as shared project files are accessed, updated, and replicated by multiple users across multiple servers on a network.

PeerLock Server provides network file locking while local shared files are in use. This ensures that when a user is modifying a file, no other user will be allowed to make changes to that file on any machine that is part of the PeerLock configuration. PeerLock integrates seamlessly with Microsoft DFSR to create a comprehensive collaboration environment.

PeerLock is an entry-level product originally designed to help organizations establish a file collaboration environment by adding file locking, a missing feature, to Microsoft DFSR. Unfortunately, many users discover the lack of file locking in DFSR after they have encountered problems with file version conflicts and corruption.

If you are not happy with the performance of DFSR or have additional requirements, check out our Solution Overview at the bottom of the page.

Main Features

  • Real-time„ Detection „of „File„ Use „and „Immediate„ Remote„ Locking
  • Cross„-Domain „File „Locking
  • Failed„ Connections „Retry
  • Instant „file„ locking„
  • Can „be„ run „as „a „service
  • Source/Target „Folder/„File„ Filter
  • Support „for „UNC „folder/path„ names
  • Easy „install „and„ unobtrusive „operation
  • Create/View „and„ close„ folder „selections „in „MS„ Windows „Explorer
  • Admin Log Reporting
 

Supported Platforms

Microsoft Windows Server 2008 - 2012 R2

Depending on the size of the organization and the location that needs to be included, Microsoft DFSR has limits on what it can handle. Because of this, Peer Software has developed a portfolio of comprehensive collaboration solutions, which are able to support larger environments with TB's of data and thousands of users around the world. The following table will give you a simplified overview of each solution and when to use it.

Peer Software File Collaboration Solutions
 MS DFSR
PeerLock

PeerLink

Read more
Supported OS Windows Windows, Data OnTap
Replication Engine Microsoft DFSR PeerLink
File Locking during transfer NO YES
Central Monitoring Console NO YES
Replication Topology Full Mesh Hub & Spoke
Supported Network Latency < 150 ms > 150 ms
Recommended Sites (*1) 3 (10) unlimited
Cross Domain NO YES
Cross AD Trees NO YES
(*1) The number in brackets represents the maximum number of sites if you do not replicate your data set in full mesh, which means you only share the data set in a 1:1 relationship like HQ - Branch Office.
The number of sites you can configure in a collaboration session depends on a number of factors including: replication topology (1:1 or n:n), WAN connectivity, and network latency, just to name some. Please get in contact with Peer before you start an evaluation so we can help you choose the right solution based on your requirements.