...
Describes how to configure periodic synchronization resources.
...
Basic
To configure a resource that performs periodic synchronization, you can configure a periodic_sync section within the node section of the configuration file. The period item in the periodic_sync section specifies the synchronization period (in seconds, minutes, or hours). The starting point at which periodic synchronization occurs is when a resource is promoted to Primary . If a resource is promoted to primary and then demoted to secondary, periodic synchronization is interrupted.
| Note |
|---|
The A periodic synchronization sync configuration only handles synchronization purely, not replication. Because it does not handle real-time I/O (replication), you must control or account for real-time changes of to the synchronization source data must be controlled by the user or operated with this in mind. |
Below is an example of a basic configuration for periodic synchronization.
| Code Block |
|---|
"nodes": [
{
"files": [
{
"path": "d:\",
"recursive": true
}
],
"periodic_sync": {
"period": "1h",
"report": "summary"
}
}
|
NFS sync
| Info |
|---|
FSR 1.2 or higher |
NFS synchronization is a configuration method that periodically synchronizes periodically with using a remote network path as the source.
...
However, the target must be configured as a local disk path of a specific node and should not be configured as an NFS path.
| Warning |
|---|
Data on the NFS path is shared by multiple clients. Among them, FSR also operates as a client, so if random writing is performed on one file without any special measures, file corruption may occur. Therefore, configuring the target as NFS is prohibited. |
NFS synchronization on Linux differs only in that the target of periodic synchronization is a remote network path. You only need to specify the pre-mounted remote path in the configuration file, such as the /samba path in the example below.
...