...
Works with at least 2GHz, 4 core or higher x86/x64 compatible processor.
Memory
...
system memory
...
It is recommended that the system have at least 4GB of memory and at least 30% of
...
the physical memory usage as free space. Typically,
...
the point at which the operating system
...
starts paging to respond to
...
memory shortage is considered to be when physical memory usage exceeds 70%. When paging is enabled
...
in the system,
...
overall I/O performance
...
may decrease, so this must be taken into
...
consideration.
...
memory buffer size
The memory buffer for replication is used to buffer the local I/O load
...
, and its size is
...
obtained by the following
...
equation.
Size of
...
maximum bandwidth transmitted per time (seconds) *
...
timeout time (seconds)
...
In the case of 1Gbps, you can
...
obtain approximately 100MB/s *
...
5s =
...
500MB, and you
...
can configure it at the level of 500MB to 1GB with more room than 500MB.
If
...
the variable band of the WAN section needs to be considered for DR configuration,
...
WAN bottleneck situation is responded to with DRX buffering
...
through DRX linkage. If DRX is not linked, allocate a larger memory buffer size
...
as described above (
...
2 to 3 times the memory buffer), and if there is no available memory space
...
, consider configuring it as a file buffer (see below).
| Info |
|---|
| However, when WAN replication (DR) is configured, if the size of the memory buffer is configured to be too large compared to the size of the band, the data accumulated in the buffer itself may act as a bottleneck, which may intensify delay (buffer bloat). Tuning may be necessary to lower the large buffer size and adjust it to an appropriate level. |
Disk
...
- Approximately 2GB is required for basic installation, including installation files
...
- , engine files, and
...
- performance logs.
- An additional 110 MB per resource is required for debug file logs.
- If you configure a
...
- file buffer, you
...
- will need
...
- disk space
...
- equal to the size of the file buffer.
...
file buffer
...
File buffer is a feature function that allows you to use regular files for buffering purposesas a buffer. However, using a file buffer involves file I/O to write to the buffer , which may result in performance degradation compared to traditional existing local I/O. File buffers To minimize performance degradation, it is recommended to configure a dedicated disk volume for the file buffer.
The file buffer can be sized to fit your needs, and are typically sized between 5 and suit the user's purpose, and the size is usually set at 5 to 10 times the size of a the memory buffer.
...
- It is based on active-passive clustering operation.
- Supports one-way replication from primary to secondary nodes. Operating methods such as circular mirroring and dual primary mode are not supported.
- Asynchronous replication is supported, but synchronous replication is not supported.
Functional scope
...
Functional scope
Replications of some system files is excluded. This is a description of the specific range of functions supported by fsr.
Disk Path
You can replicate the path of a regular local disk. Remote paths such as NFS cannot be replicated (NFS paths only support source operation for periodic synchronization).
File Types
The following file types are supported.
- general files and directories
- link files
- soft link
- hard link
- junction, reparse point
- sparse file
- compressed file
- encrypted file
...
- special file
- NTFS ADS(Alternate Data Stream)
- NTFS TxF(Transaction File)
| Info |
|---|
When a user specifies a replication target for an FSR, care must be taken to ensure that Be careful not to specify system files used at by the OS level are not specified as replication targets. Even if there is normally no problem in replicating Duplicating system files , care must be taken as it can cause operational problems if a deadlock occurs occasionally due to contention with file I/O of the OS during synchronization or replicationmay cause unexpected problems, such as replication competing with system I/O. This includes system files, driver files, swap files, OS installation path (Windows path), etc. |
| Info |
|---|
|
I/O Types
Most of the I/O types supported by Windows and Linux are supported.
...
| Info |
|---|
|
Shared Files
Real-time replication of files shared by remote network filesystems (NFS, SMB, etc.) is not technically possible. This is because the entity performing the I/O to the shared file data spans multiple nodes, so replication cannot be achieved by simply filtering the local filesystem where the FSR is installed.
...
| Info |
|---|
For HA operation, the principle is to configure the source and target systems with the same security account status. However, it is realistically difficult to configure the security configuration of the source and target systems to be completely identical and may not conform to the customer's security policy. Even if the security configuration status of the source and target are different, FSR replicates files based on the security identifier (SID) of the files on the source side to ensure that there are at least no problems with the replication operation. Afterwards, in order to access the copied files in the target, follow-up measures, such as adjusting the target's account and permissions, must be followed. |
Operation Method
- It is based on active-passive clustering operation.
- Supports one-way replication from primary to secondary nodes. Operating methods such as circular mirroring and dual primary mode are not supported.
- Asynchronous replication is supported, but synchronous replication is not supported.