View Attach (6) Info

Add new attachment

Only authorized users are allowed to upload new attachments.

List of attachments

Kind Attachment Name Size Version Date Modified Author Change note
png
 john_doe.png 46.6 kB 1 29-Dec-2020 05:25 Ben Spink
png
 replication.png 107.6 kB 2 29-Dec-2020 05:25 Ben Spink
jpg
 replication1.jpg 374.8 kB 1 11-May-2021 10:52 Ada Csaba
jpg
 replicationdbg.jpg 239.5 kB 1 20-Jul-2021 19:33 Ada Csaba
png
 user_homes.png 46.8 kB 1 29-Dec-2020 05:25 Ben Spink
png
 vfs_properties.png 38.9 kB 1 29-Dec-2020 05:25 Ben Spink

This page (revision-30) was last changed on 20-Jul-2021 19:37 by Ada Csaba

This page was created on 29-Dec-2020 05:25 by Ben Spink

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Difference between version and

At line 1 changed 2 lines
!!Background
File based replication can be configured between CrushFTP servers. CrushFTP uses a journaled file transfer system to make sure data changed on one server is changed the same way on both servers. Conflict scenarios should be very rare and difficult to achieve. However, we do not recommend the journaled system as the first choice method if you have a shared storage option available between servers. The journaled system should be the secondary choice when its necessary due to geographically distributed servers. The journaling and replication can *only* account for changes being made through CrushFTP. No outside processes can modify files, write to files, rename files, etc. All access needs to go through CrushFTP, or your journaled system will be out of sync requiring manual intervention to try and correct things. Replication requires an enterprise level license, it is not available in normal licenses.\\
!!Enterprise-only feature, not available with Normal licenses.\\
A set of features to facilitate clustering. It allows independently to keep in sync the local user database, server preferences, Jobs and replicate file operations issued by user accounts, automation Events and Jobs. The two subfeature sets work independently from each other.\\
----
At line 4 changed 2 lines
!!Preferences
Go to your preferences, Replication tab.\\
[{Image src='replication1.jpg' width='..' height='..' align='left' style='..' class='..' }]\\
----
At line 7 changed 4 lines
[{Image src='replication1.jpg' width='..' height='..' align='left' style='..' class='..' }]
\\
!VFS Replication
!User database and Server settings replication\\
Configured on the upper half of the page (green highlight). Each cluster node must be point towards the other node(s) IP or hostname and replication port. Network firewall between nodes must allow two ways traffic on the replication port.\\
The checkboxes toggle replication of server components. IP port bindings and the replication settings themselves are excluded from replication.\\
;Server Host Port: IP (or hostname) port pair, pointing to the mirror server node. In case of more than 2 nodes clustered, the field accepts comma separated list of all other nodes' IP port pair.
;Replicate User Manager Changes: toggle replication of the local XML user database. If using an external SQL database, this option has to be turned off.
;Replicate S3Crush protocol: applies only when using the __s3crush://__ VFS protocol. Toggles replication of the local S3 database. Needs to be turned off when using default __s3://__ VFS protocol. In all other scenarios, ignored.
;Replicate Job Changes: toggle replication of Jobs. Need to complement with [ServerBeat], to prevent all cluster nodes running the same jobs concurrently.
;Replicate HTML reports: toggle replication of scheduled Reports.
;Replicate Shares: toggle replication of [temporary accounts|sharing]
;Replicate Preferences: toggle replication of server preferences, except [IP port bindings|IP Servers]
----\\
!Files Replication:
At line 49 added 2 lines
----
\\
At line 56 added 2 lines
----
\\
At line 46 changed one line
If the opposite server goes offline, this folder will start to fill up with uploads that are pending to be delivered to the opposite server. If there is a conflict scenario where a replicated action cannot be performed on the opposite server, you will have to manually look through this folder, sorted by date, and decide what to do with the replication item that cannot be processed.\\
If the opposite server goes offline, this folder will start to fill up with uploads that are pending to be delivered to the opposite server. If there is a conflict scenario where a replicated action cannot be performed on the opposite server, you will have to manually unblock by killing the error replication item on Server Admin->About page. Or look through the "multi_journal" folder, sorted by date, and decide what to do with the replication item that cannot be processed.\\
[{Image src='replicationdbg.jpg' width='800' height='..' align='left' style='..' class='..' }]\\
Version Date Modified Size Author Changes ... Change note
30 20-Jul-2021 19:37 5.546 kB Ada Csaba to previous
29 20-Jul-2021 19:34 5.43 kB Ada Csaba to previous | to last
28 11-May-2021 11:38 5.335 kB Ada Csaba to previous | to last
27 11-May-2021 11:37 5.327 kB Ada Csaba to previous | to last
26 11-May-2021 11:37 5.327 kB Ada Csaba to previous | to last
25 11-May-2021 11:36 5.34 kB Ada Csaba to previous | to last
24 11-May-2021 11:35 5.327 kB Ada Csaba to previous | to last
23 11-May-2021 11:35 5.327 kB Ada Csaba to previous | to last
22 11-May-2021 11:33 5.248 kB Ada Csaba to previous | to last
21 11-May-2021 11:32 5.259 kB Ada Csaba to previous | to last
« This page (revision-30) was last changed on 20-Jul-2021 19:37 by Ada Csaba
G’day (anonymous guest)
CrushFTP10 | What's New

Referenced by
CrushFTP8New
High Availability
LeftMenu

JSPWiki