Skip to end of metadata
Go to start of metadata

For installation and configuration refer 

FileCloud ServerLink is a feature to replicate a FileCloud site to another location. Changes in one FileCloud server are seamlessly replicated to another site,
Replicated data includes the following:

  • Files and Folders (Managed Storage Only)
  • User Accounts
  • User Groups
  • Comments
  • Favorites and Favorite Lists
  • File and Folder Shares
  • Folder Level Permissions
  • Metadata

ServerLink can be useful in several deployment scenarios.

  • An organization having a headquarters in one geographic location but many branches in other locations spread across the globe. If there is a single FileCloud server serving the headquarters, the branch offices will observe increased latency when accessing files remotely. To alleviate the problem the branch offices can each have their own FileCloud Site with each being a mirror of the main FileCloud site at HQ. Each branch office FileCloud site is a slave to the master FileCloud site at HQ.
  • An organization might want a FileCloud site locally on the LAN for fast local access and a remote site on the cloud for remote file access. In this case the local FileCloud site can be connected by serverlink to the remote FileCloud site on the cloud to keep data replicated.
  • An organization might want another FileCloud site as a standby or backup so that if the primary site goes down then the standby can be available for operation.

FileCloud replication has the concept of a master site and a slave site.

There can be many slave sites connected to a master site. Typically, there would be one master site and multiple slave sites.  Changes that happen in the master replicate to the slave. Similarly changes that happen in the slave replicate to the master. When there are multiple slaves, if a change happens in one slave, that change is propagated to all slaves as well as the master. 

Replication is done by running the replication client on the slaves. Replication clients are not required to be run on the master.

  • ServerLink keeps entire sites in sync with each other (ie mirrors), it is not possible to only keep part of the site in sync with another site.
  • Although ServerLink tries to replicate changes as fast as it can, replication is not instantaneous and changes in one site can take some time before it is propagated to the other site. Users and Administrators should be aware of this fact and make sure their business processes take into account. 
  • Changes occurring to both sites on a single file will result in the change in the master site "winning" out. The other version changed in the site will be available in the "previous versions" and might never make it to the master site. In most conflict scenarios like these, the master site's change will apply and overwrite the slave site changes. The recommendation is to avoid working on same sets of files in master and slave at the same time. 

  • File Locking is not enabled by default.
  • File Locking is not propagated between servers. So if a file is locked in one server and modified in another, the change can be still pushed into the server where it is locked. 
  • Team Folders are replicated ONLY if Team Folders are enabled in Admin settings both in master and slave.   For more information on this, refer Team Folders

  • No labels