...
1:1 replication configuration for source and target nodes.
Inc drawio | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
1:N
1: N replication configuration that simultaneously replicates one source node to multiple target nodes.
Inc drawio | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
N:1
N:1 replication method with multiple nodes as source and one node as target.
Inc drawio | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Local Replication
This is a way to specify the source and target of replication to one node. It is used to do local backup or local migration without separate target node.
Inc drawio | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Shared Volume Replication
A configuration in which one source data is shared by two (active-standby) nodes and replicates this source data to the target node. Shared volumes can be storage volumes in the form of SANs, shared volumes in NFS.However, replication for NFS shared volumes cannot track real-time changes of data to be replicated because FSR cannot control all client hosts that access the shared volume a third target node. This approach is used when a SAN-like storage shared volume is shared by two nodes simultaneously and replicated to DR in real time.
Inc drawio | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Periodic synchronization
This is a configuration method for volumes that only perform periodic synchronization. It does not perform real-time replication. In particular, volumes that cannot perform real-time replication, such as remote NAS shared volumes, can be backed up periodically using this method.
The target can be DAS or NAS, but in the case of NAS targets, FSR cannot be installed on the NAS, so it must be ensured that no writes occur to the target resource (to maintain consistency).
Inc drawio | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
However, be sure to specify synchronization for NFS shared volumes as a source only, and not as a synchronization target. Because NFS shared volumes are written to by multiple clients, you cannot control the FSR engine as a single synchronization target. For more information on this, see Periodic synchronization in the appendix.
Info |
---|
Replication to an NFS shared volume is technically impossible to track every change to the data being replicated in real time because, due to the nature of network shares |
...
, you cannot control every random client host that accesses the shared volume. |
Configuration File
The configuration file is a json format text file that describes the configuration type and attributes of the replication. It is described as a system configuration file and a resource configuration file. The system configuration file specifies node global paths necessary for FSR operation, and the resource configuration file describes the specifics of replication such as ip address, replication target, and handler. Basically, the configuration file should be created by hand. If you want to change the properties of a running resource, modify the configuration file and apply it by executing adjust command using CLI or REST-API.
...