Periodic synchronization

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.

A periodic sync configuration only handles synchronization, not replication. Because it does not handle real-time I/O (replication), you must control or account for real-time changes to the synchronization source data.

Below is an example of a basic configuration for periodic synchronization.

"nodes": [ { "files": [ { "path": "d:\", "recursive": true } ], "periodic_sync": { "period": "1h", "report": "summary" } }

NFS sync

FSR 1.2 or higher

NFS synchronization is a configuration method that periodically synchronizes 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.

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.

"nodes": [ { "files": [ { "path": "/samba", "recursive": true } ], "periodic_sync": { "period": "1h", "report": "summary" } }

NFS sync on Windows requires you to specify a path to a network drive that is allocated from your user account, which causes basic permission issues. To do this, you need to perform the following preliminary tasks through the help command for nfs provided by FSR.

This command adds network drive mapping to FSR.

fsradm nfs add <UNC-remote-path> -u <username> -p <password>

C:\>fsradm nfs add \\NODE2\SHARED -u smgo -p password done

And organize your resources. The path must be written as a UNC remote path.

Depending on the network situation, the nfs remote connection may be disconnected or there may be a problem. In this case, you can try reconnecting using the nfs connect command.