DRX requires sufficient enough free physical memory for DRX's buffering capability when installed locally in an operating machine environmenton the production server. If you do there is not have enough free physical memory space, you should also consider adding increasing the physical memory on your of the production machineserver.

Also, if you use the compression feature to accelerate replication, you should be aware consider that compression can may cause CPU load on the operating node. Compression can be used locally if production server. If the local I/O load is not heavily burdened and compression heavy and the performance degradation of the operating node is insignificant. However, if compression loads affect performance across the local system, you should rethink the use of compression. Compressed loads can result in an additional load of approximately 20 ~ 30% on production node due to compression is minimal, it is not a problem, but if the compression load affects the performance of the local system as a whole, you should reconsider using compression. Compression load can add about 20-30% of the local I/O load . If and can be offloaded by configuring the DRX that performs the performing compression is configured as a dedicated machine and separated separating it from the operating environment, it is possible to distribute the load depending on the compression. These DRX operational policies should be production environment.

The operating policy of such a DRX should be established based on preliminary data on the local I/O load, and should be determined by preliminary investigation of the following items in the configuration environment

2.1. Prior research

2.1.1. Operating System

Windows 2008 or latershould be investigated to determine the appropriate specifications and buffer operating policies for the DRX to run.

Specifications

Operating Systems

Supports Windows 2008 and later 64-bit, Linux CentOS 6.4 or and later, and Ubuntu 12.04 LTS or and later 64-bit platforms are supported.

Minimum Specifications

2.1.2. Operating machine minimum specification

...

• Minimum 1 GHz or faster x86/x64 compatible processor (

...

• 2 GHz or

...

• faster recommended), minimum 4

...

• cores recommended
• At least

...

• 4 GB of physical memory

...

• Minimum 10 GB capacity disk

Recommended Memory Specifications

DRX's physical memory specifications are variable depending on the number of resources, maximum I/O, and transfer bandwidth. The following is a formula for DRX's physical memory specifications when the maximum I/O is greater than the transmission bandwidth.

• Number of Resources * (Average I/O (MB/s) - Bandwidth (MB/s)) * I/O duration (seconds) + compression/encryption buffer (2GB)

If the peak I/O is always low compared to the bandwidth, calculate the size of the buffer per resource to be 1 GB to determine the physical memory specification.

• Number of resources * 1 GB + compression/encryption buffer (2 GB)

WAN bandwidth is not really a guaranteed bandwidth, but rather a variable bandwidth that fluctuates based on network conditions. In general, WAN bandwidth is considered to be in the range of 10 to 100 Mbps, and estimating 1 MB/s to 10 MB/s is appropriate from a buffering perspective. Also, it is not advisable to disregard DRX buffering just because the maximum I/O measured within a period of time is lower than the replication bandwidth. Depending on the characteristics of the applications in the operating environment, there may be situations where the maximum I/O spikes at an unspecified time, so it is advisable to configure the DRX buffer with extra space for such situations.

The following is an example of determining the physical memory specification that DRX can buffer for 30 seconds of I/O at an average of 100 MB/s over a 100 Mbps WAN bandwidth.

The following is an example of determining the physical memory specification assuming a WAN 100 Mbps bandwidth, a maximum I/O of 500 MB/s, and a maximum I/O duration of 30 seconds. In this example, the required memory for one replication resource operation is 20.7GB (32GB recommended).

...

Number of resources

You can configure it to any size as long as as many resources as your memory resources allow and limit it to up to 100 channels of replication resources.

...

. The maximum resource is 100 channels, but this can be flexible depending on available memory, and if the number of resources you need to operate is more than a few dozen channels, you may want to consider investing in multiple dedicated DRX nodes.

Preliminary Server I/O Load Survey

Use the following procedure to measure the I/O load on of the production server.

• Measure the read/write I/O

...

• data of the production server

...

• replication target disk (average I/O, maximum I/O

...

• over a

...

• period of at least 1-4 weeks).

...

• Measurement method
  • Windows:

...

• • Use Performance Monitor tool

...

• • to collect disk I/O

...

• • statistics data

...

• • Linux:

...

• • Use utilities such as iostat

...

• • to collect disk I/O

...

• • statistics data

...

• Consider buffer size, compression, and

...

• buffer operation policies based on the measurement results

...

...

Replication bandwidth

Replication bandwidth requires bands require at least 10 Mbps to 100 Mbps bandwidth.

...

Policy

Determine how you will configure your operating environment your configuration based on the I/O load of your environment and whether you are using compression is enabled. the local configuration is . Local configurations are common, but If the replication load is large and WAN section acceleration is required, a dedicated configuration is recommended.

2.3. Buffer sizing policy

...

dedicated configurations are recommended when replication loads are high and acceleration across the WAN is required.

Buffer policy

• Preliminary research on network bands, operating machine I/O load

...

• factors is required to instrument DRX's physical buffer specifications.
• Pre-survey items
  • Average I/O per

...

• • resource on the production machine
  • Maximum I/O

...

• • volume
  • Maximum I/O

...

• • duration
• The average I/O and maximum I/O

...

• figures of the

...

• production machine are the basis for building an appropriate buffering environment.

The DRX's buffer should be set to an the appropriate size to accommodate handle the I/O load values of the pre-investigated operating nodesthe production node based on the preliminary survey. If the I/O data based on the preliminary investigation can not be obtained, it is necessary to perform the tuning process on survey is not available, the buffer size should be tuned after the configuration and trial operation according to piloting based on the recommended buffer specification based on the specifications in case 1.

If the I/O load on the operating production node is too excessively large and the maximum duration of peak I/O duration occurs over a long period of time (several minutes to several tens of minutes), DRX buffering can may not be difficult able to handle it. In this case, you should consider think about data compression.

...

BSR

Congestion policy

The congestion state means that buffering is impossible because there is no free space in the DRX buffer because the replication load is increased. In this case, DRX does not perform any special action and concentrates on remotely transmitting the replicated data in the buffer. The response to the congestion state is left to the congestion policy of DRBD.

...

resource r0 {
	proxy {
		memlimit 1G: # DRX 버퍼buffer
	}
	net {
		on-congestion pull-ahead; # Congestion policy setting (Ahead mode)
		congestion-fill 950M; # Set congestion awareness point (when 950Mbyte data is buffered is congestion point)
	}
}

The congestion policy of DRBD is as follows. It is recommended to set Ahead mode for WAN interval asynchronous replication operationBSR has the following three congestion policies, and Ahead mode is recommended for asynchronous replication across the WAN.

• block:

...

• Wait for I/O

...

• until the buffer is

...

• empty (until it can be queued

...

• into the buffer). This is the default when no congestion policy is set.
• disconnect:

...

• Disconnect the replication connection and enter the StandAlone state.
• pull-ahead:

...

• Enter lazy replication mode.

...

• In this

...

• case, the replication connection is maintained, but replication is stopped and local I/O is

...

• logged as out-of-sync,

...

• but resynchronization of the logged out-of-sync

...

• is performed when

...

• congestion

...

• is released.

2.3.2. Buffer Size Tuning

...

Specifying buffer size

• BSR coupling assumes an Ahead mode (

...

• lazy replication), asynchronous replication configuration.
• Ensure that measurements can only

...

• be taken over measurement segments where the replication connection is maintained

...

• ; I/O measurements

...

• over disconnected segments are not considered.

...

• Aggregate the number of times

...

• BSR enters Ahead mode (

...

• congestion

...

• entry count) using the following

...

• methods
  • Aggregate the number of times the "Congestion-fill threshold reached"

...

• • output in the BSR log.
  • Check the number of Ahead entries

...

• • via the

...

• • bsrsetup events2 command

...

• Resize the buffer based on the

...

• collected congestion entry counts. If the congestion frequency

...

• is

...

• high, the size of the buffer should be further increased.
• If the

...

• congested section does not

...

• become less frequent after increasing the buffer

...

• , consider compression.

2.4. Physical Memory Specifications

DRX's physical memory specifications are variable based on number of resources, maximum I/O, and network bandwidth. The following is a formula for DRX's physical memory specification when the maximum I/O is greater than the bandwidth.

• resource count * (max I/O(MB/s) - bandwidth(MB/s)) * max I/O maintained interval (sec) + compression/encryption buffer(2GB)

If the maximum I/O is always lower than the bandwidth, the physical memory specification is determined by calculating the per-resource buffer size as 1GB.

• resource count * 1GB + compression/encryption buffer(2GB)

WAN bandwidth is virtually variable. Since the WAN bandwidth generally has variable bandwidth characteristics that vary widely depending on the network conditions, not the guaranteed bandwidth, it is generally considered that the WAN bandwidth is estimated to be 1 to 10 MB/s, It is appropriate. Also, it is not recommended to consider disabling of DRX buffering because the maximum I/O measured within a period of time is lower than the replication bandwidth. Depending on the characteristics of the application in the operating environment, there may be a situation in which the maximum I/O surges at an unspecified point. Therefore, it is preferable to allocate free space in the DRX buffer for this situation.

The following is an example of determining the physical memory specification assuming a WAN 100 Mbps bandwidth, a maximum I/O of 100 MB/s, and a maximum I/O duration of 30 seconds. In this example, the required memory for one replication resource operation is 6.7GB (16GB recommended).

...

Normal speed

(100MB/s)

...

max 2GB

...

The following is an example of determining the physical memory specification assuming a WAN 100 Mbps bandwidth, a maximum I/O of 500 MB/s, and a maximum I/O duration of 30 seconds. In this example, the required memory for one replication resource operation is 20.7GB (32GB recommended).

...

High speed 구성

(500MB/s)

...

2GB

...

FSR

FSR only needs to specify the size of DRX's buffer. It does not support congestion mode, so it does not need to be set. If the DRX buffer is full while buffering, it will immediately empty the buffer and automatically move to a synchronized state.

When specifying the size of the buffer, you only need to refer to BSR's buffer policy to set the criteria for buffer operation and consider sizing accordingly. You can specify buffers as large as your memory allows, typically at the multi-GB level.