Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents


Main Features


Synchronization

Inc drawio
simple0
zoom1
custContentId3620143748
pageId1061127806
diagramDisplayNameFSR_resync_basic.drawio
lbox1
hiResPreview0
baseUrlhttps://mantech.jira.com/wiki
diagramNameFSR_resync_basic.drawio
imgPageId1070399557
pCenter0
aspectKh710xyq81amoqJS_zdP 1
includedDiagram1
width530
aspectHashe559920f494dcec6484d3ec2ea05f3920f9a3fbc
linksauto
tbstyletop
height391

...

Synchronization can also be done manually by the user, for example, by issuing a sync command, configuring periodic synchronization, etc.


Replication

Inc drawio
simple0
zoom1
custContentId3172368511
pageId1061127806
diagramDisplayNamefsr basic concept
lbox1
hiResPreview0
baseUrlhttps://mantech.jira.com/wiki
diagramNamefsr basic concept
imgPageId1070399557
pCenter0
aspectCGzCTaqGlybdCWYpRhP1 1
includedDiagram1
width661
aspectHashe9e4e0c48f07d92594f917b0a89a56951e8afdb9
linksauto
tbstyletop
height421

...

FSR supports asynchronous replication by default. Asynchronous replication performs internal buffering to minimize the impact of local I/O latency, and the size of the buffers used should be set appropriately for your environment. Buffers are provided as memory buffers and file buffers, and their size is set within the available memory and disk limits of the system.


Online File Verification

Online File Verification of FSR is a function to perform file-level hash summarization, list, and real-time comparison of duplicate file SET of source node and target node. If there is a difference in the results of the comparison, the FSR informs the user and can resolve the difference by resync.

...

For more information, refer to Online Verification


Optmization

Replication is difficult to maintain target consistency when the transmission bandwidth is low depending on the operating environment. In situations where the replication environment is not physically backed up, FSR provides the ability to optimize the transmission load by compressing the transmitted data and simultaneously perform real-time encryption as needed.

It also provides the ability to efficiently use the public network band by arbitrarily limiting the replication transmission band according to the operating situation. For more information, refer to Etc.


Split-brain

...

FSR automatically detects split brains. This feature is not available in other commercial file replication solutions and is a unique feature of the FSR solution. In other file replication solutions, the detection of split brain is left to the operation of the HA solution. However, this approach is dependent on HA operations, and in some situations can cause data loss due to reverse sink. To fundamentally avoid this problem, the replication solution must track the status of the file and automatically detect the split brain to prevent data loss.

...

detection

In case of unintended and unusual situations during replication operations, measures are required to protect data on the source side. Among them, if a primary becomes a secondary (spli-brain) at some point after disconnection, potentially causing data loss, it should be automatically detected and acted upon to block replication, a feature called split-brain detection. For more information about this, see Split-brain in Troubleshooting.


Statistics

It provides statistical information that monitors the operation of replication and provides real-time performance monitoring. For more information, refer to Checking Status

Snapshot

In addition to performing real-time replication to the target node, it provides a snapshot function to back up data at a specific point in time to a separate space. For more information, refer to 5.5. Snapshot



Terms


Node

A generic term for devices connected to a network, of which computer nodes are called hosts. Normally, node and host tend to be used without distinction. In this manual, node is used with the same meaning without distinguishing from host.

Cluster

A cluster is a collection of computer nodes for special purposes. The cluster here is a replication cluster, which contains the source and target nodes that are configured to perform replication, and the FSR represents these replication clusters on a resource basis.

Resource

A resource refers to a replication resource and is a unit that provides replication services. A resource consists of a node, a connection, and a (set of replication) filesets, which can be represented by an FSR configuration file. FSR interprets the replication environment and settings through a configuration file and performs replication based on this.

Source(Primary)

Source data nodes on a replication cluster are called source nodes or sources. And the role in the replication cluster is Primary.

Terms such as primary, source, and active nodes are used differently depending on the replication or HA environment, but are not usually strictly distinguished.

Target(Secondary)

The node that receives the original or incremental data on the replication cluster and maintains a copy is called the target node or target. And the role in the replication cluster is Secondary.

...

Info

For replication, Primary is always the source and Secondary is the target, but for synchronization, the secondary can also be the source. This is because even if only secondary nodes exist in the replication cluster, they must be allowed to synchronize based on the latest secondary.

File Set

A unit within a resource that describes a replication target. A fileset is described as a file or directory to be replicated and contains an exclusion filter. An exclusion filter is a policy that allows you to exclude some files or directories from replication targets. It is based on regular expressions such as wildcards.

Consistency

Represents data integrity, which means that the data on the source and target is exactly the same. File replication ensures byte-level data consistency.

Split-Brain

A split brain is a condition or status in which two or more nodes have a primary role at any point in the replication cluster, potentially causing data loss. When a split brain occurs, the user can decide which node has the primary role to sacrifice and resolve the split brain to normalize the replication.

RID

FSR maintains and tracks a ULID-based unique number that represents the file state of a fileset to be replicated. This value is called the revision identifier (RID). The FSR uses the RID to determine the direction of synchronization and identify the split brain.

Topology

FSR can configure various connections between nodes depending on the replication configuration. Typically operating in a mesh or star topology.

...