Server Collaboration

Article ID: KBA-01108 Last Review: N/A Revisions: 1.1 Download PDF

Purpose & Scope:

Real-Time collaboration of two or more servers, for purposes of data availability.

Procedure:

Preparation:

Each server involved in the collaboration should be able to see the remaining servers through a UNC share. The PeerSync, PeerLock and PSlistener (ByteReplicator) installation should be installed on each Server where the data is being accessed and modified.

The following tutorial is based on a many-to-many collaboration between 3 servers. Each server will be in charge of replicating to the remaining servers in a real-time bi-directional mode. The PeerLock on each server will also be in charge of locking the files on the remaining servers.

Requirements

=============================================

PeerSync Server Edition (x # of server)

- Multi-Threading (x # of server)

- ByteReplicator (x # of server)

PeerLock Server (x # of server)

OR

PEER Collaboration Package (x # of servers)

=============================================

Please follow the steps below sequentially to make sure you properly configure each component.

SETUP REAL-TIME BI-DIRECTIONAL

In order to Setup PeerSync to run in a bi-directional synchronization you would want to use the tutorial below for the configuration of each of your PeerSync Profiles (for this tutorial we have machine A, B and C).

A Server Profile

A<-->B

A<-->C

B Server Profile

B<-->A

B<-->C

C Server Profile

C<-->B

C<-->A

All the profile jobs will be configured in a bi-directional real-time mode. For a tutorial on real-time bi-directional, please see the Additional Resources section of this article.

RECCOMENDATIONS:

You want to make sure all the temp files are excluded from the sync on all the locations. Sometimes the temp files may interfere with the PeerSync file copy process. Some of the applications (such as excel) have temporary files without an extension and in order to exclude these you want to make sue you add the following:

1) Go to Exceptions-->Include Files

2) This field should have the following *.*

Do the above for all the jobs, unless you have some files that you wish to be processed that do not have an extension. Including the *.* will only include files with an extension.

Also please make sure all your jobs have the following for the Exclude Files field as well as any other temp files you may know your specific applications create.

*~*; *.tmp; *.temp;

Once you have all four Profiles configured, you want to start 1 PeerSync at a time and wait until the first PeerSync (a) has completed the initial scan of the two jobs in order to start the Second PeerSync (b) and so on for the third (c).

ENABLE MULTI-THREADING

• Multiple copy threads and job threads within the PeerSync ProfileàOptions Commands screen. We recommend initially testing with a maximum of 5 Job threads and 10 Copy threads. Depending on the system can handle this amount of activity you may increase these at your discretion.

SETUP TO RUN AS A SERVICE

Once you have these two profiles up and running I would suggesting launching the 3 from the Run/View Current Profile as an Application and testing that it all works when running as an application.

Once you have confirmed that the real-time bi-directional works for all machines in an application mode and not a service, then you would use the link below to setup the two PeerSync Profiles to run as a Service independet from the logon user (Make sure your remote folder path is specifyid with a UNC path instead of a Mapped Letter Drive).

PSListener/ByteReplicator Configuration

To configure the Byte-Replicator you would want to enable the byteReplicator option within the PeerSync Profile(s) for the specific Job you are running in a Real-Time bi-directional synchronization. You would then save the Profile(s) from both machines. and Install the PSListener application on both machines running as a Service under and Administrator's account. Use the information included in the manual below for this setup.

Once you have the PSListener running as a Service on both machines. Restart the PeerSync Service on the 3 locations to pick up the changes in the Profile just made (enable of ByteReplicator).

PeerLock Configuration

Install PeerLock on the 3 locations and set it up to run as a Service under an administrator's account. PeerLock is configured similar to PeerSync by specifying the watched source folder and the target folder. Use the same source target folder used for the PeerSync Profile of that machine. Do the same on machine B, and C.

Applies To:

Additional Comments:

Additional Resources:

See KB Articles:

KBA-01049 (Configuring Bi-Directional Real-Time)

KBA-01040 (Setup PeerSync to Run as a Service)

Help Guides:

PeerSync: http://www.peersoftware.com/products/resources/pdf/kb/ps/hlp/pshelp.pdf

PeerLock: http://www.peersoftware.com/products/resources/pdf/kb/pl/hlp/plhelp.pdf

PSListener: http://www.peersoftware.com/products/resources/pdf/kb/br/hlp/PSListHelp.pdf