What the DRX should be configured for is the configuration of individual replication resources and the global settings configuration that the DRX requires to run. Settings for the individual resources are configured through the drbd.conf file and the global settings are configured through the drx.conf file.

• The drbd.conf file describes replication connections, buffer sizes, and optional settings. By default, it is created in the same way as the DRBD configuration file format. In most cases, DRBD is installed locally and will be created by modifying the already created drbd.conf file.
  • For more information on the DRBD configurationfile format, see https://docs.linbit.com/man/v84/drbd-conf-5/
• If DRBD is installed locally, DRX automatically recognizes the path of the configuration file through the environment variable (DRBD), so you do not need to change the path of drbd.conf. /etc/drbd.conf is the default path and you can change the path through drx.conf.
• If you are adjusting DRX's own options, create a drx.conf file. You do not need to create it unless it is a special case.

4.1. Configuration files

DRX is recommended to unify the configuration file of each node into the same "drbd.conf" file for the sake of management but it is not mandatory, and configuration contents of each node can be changed according to the configuration method, and the configuration file name, Can be specified separately. The major configuration items of DRX are as follows.

• Connection configuration: Setting DRX inbound IP and outbound IP address to work with DRBD
• Buffer Configuration: Set buffer size per resource (channel)
• Compression/Encryption Configuration: Setting the compression/encryption function ON / OFF

DRX sets the buffer size in the "proxy" section within the DRBD configuration file and sets the DRX IP address in the "proxy on" section within the host section. Compression and encryption settings are described in the plugin subsection in the proxy section. The following is a basic DRX configuration form, with slightly different 1:1 and 1:N replication configurations.

4.1.1. Local configuration

On node1 and node2 local systems, the DRX is installed and operated, and the contents of node1 and node2 are identical for both nodes.

• The following are examples of 1:1 replication configurations and 1:2 replication configurations.

• Note that each port information must be subject to exception handling by the firewall and configured so that no redundant ports are used.

...

resource r0 {
    device d minor 1;      
    disk d;                 
    meta-disk f;           

 	net {
        protocol A;
		sndbuf-size 20M;
		on-congestion pull-ahead;
		congestion-fill 480M;
		ping-timeout 30;
    }

	proxy {
      	memlimit 500M; # DRX TX Buffer
		plugin {
			#compressor zlib level 1;
			#crypto openssl;
		}
  	}
 
	on node1 {
        address   10.10.0.250:7789;
        node-id 0;          
        proxy on node1 {
            inside 10.10.0.250:7790;
            outside 10.10.0.250:7791;
        }
    }
    
	on node2 {
        address   10.10.0.253:7789;
        node-id 1;
        proxy on node2 {
            inside 10.10.0.253:7790;
            outside 10.10.0.253:7791;
        }
    }
}

...

...

DRX requires configuration of individual replication resources and global settings required to perform drx. Configuration for individual resources is done in the proxy section of each replication configuration file, and global settings are configured through the drx.conf file.

All configuration below is based on working with Block Replication (BSR). For integration with File Replication (FSR), see Configuring file replication in the appendix.

• If BSR is installed locally, you do not need to change the path to its configuration file as DRX automatically recognizes it through an environment variable. /etc/bsr.conf is the default path and can be changed through drx.conf.
• It describes replication connections, setting buffer sizes and options, etc. By default, it's written in the same format as the BSR configuration file, and you'll usually end up modifying some of the contents of bsr.conf that was already written when BSR was installed locally (see Format of the BSR configuration file).

Configuration Properties

The main configuration properties are:

• Connections: Set the DRX inbound IP and outbound IP addresses to work with replication.
• Buffers: Set buffer size per resource (channel)
  • memlimit
  • rx-memlimit
• Compression/Encryption: Set compression/encryption features ON/OFF

DRX sets the buffer size in the "proxy" section within the replication configuration file and the IP address in the "proxy on" section within the host section. Compression and encryption settings are described in the plugin subsection within the proxy section. Below is the basic DRX configuration form, with some differences between 1:1 single replication and 1:N multi-replication integration.

Local configuration

• With DRX installed and running on node1 and node2 local machines, the contents of "bsr.conf" on node1 and node2 are the same on both nodes.
• The following is an example of a 1:1 replication configuration and a 1:2 replication configuration.
• Note that the respective port information must be exceptionally handled by the firewall and configured so that there are no redundant ports.

resource r0 {
    device d minor 1;      
    disk d;                 
proxy on node2 {   meta-disk f;           

 inside 100.100.100.41:7790;	net {
        protocol A;
		sndbuf-size  outside 100.100.100.41:7791;
   20M;
		on-congestion pull-ahead;
		congestion-fill 480M;
		ping-timeout 30;
    }

	proxy {
  } 
}

resource r2 {
  startup {
      wfc-timeout 3;
  }
  
	proxy    	memlimit 500M; # DRX TX Buffer
		plugin {
			#compressor zlib level 1;
			#crypto openssl;
		}
  	}
 
	on node1 {
      memlimit 500M  address   10.10.0.250:7789;
  }      net {node-id 0;       protocol A;  
    verify-alg crc32c;   proxy on node1 {
on-congestion pull-ahead;          sndbuf-size 20M; inside 10.10.0.250:7790;
    congestion-fill 480M;       ping-timeout 30outside 10.10.0.250:7791;
  }    device e minor}
2;   disk	e; }
 meta-disk	g "C:/r2_meta.vhd";  
 	on node1node2 {
    node-id	1;    address   10.10.0.253:7789;
 }   on node2 {     node-id	2 1;
  }      proxy on node3node2 {
       node-id	3;     }
inside 10.10.0.253:7790;
    connection DR-node1-node3 {   	 host node1 addressoutside 10010.10010.1000.9253:66777791;
 via proxy on node1 { 	 	inside 100.100.100.9:6678;
	 	outside 100.100.100.9:6679;
	 }
	 host node3 address 100.100.100.11:6677 via proxy on node3 {
	 	inside 100.100.100.11:6678;
	 	outside 100.100.100.11:6679;
	 }
  }

  connection DR-node2-node3 { 

	 host node2 address 100.100.100.10:6680 via proxy on node2 {
	 	inside 100.100.100.10:6681;
	 	outside 100.100.100.10:6682;
	 }
	 host node3 address 100.100.100.11:6680 via proxy on node3 {
	 	inside 100.100.100.11:6681;
	 	outside 100.100.100.11:6682;
	 }
  }

  connection {
    host node1 address 10.20.25.9:6677;
    host node2 address 10.20.25.10:6677;
  }
}

global { }
    }
}

resource r0 {
    device /dev/bsr1;
    disk /dev/sdb1;
    meta-disk internal;

 	net {
        protocol A;
		sndbuf-size 10M;
		on-congestion pull-ahead;
		congestion-fill 480M;
		ping-timeout 30;
    }

	proxy {
      	memlimit 500M; # DRX TX Buffer
		plugin {
			#compressor zlib level 1;
			#crypto openssl;
		}
  	}

    on node1 {
        address 100.100.10.31:7789;
        proxy on node1 {
            inside 100.100.10.31:7790;
             disable-ip-verificationoutside 100.100.10.31:7791;
       usage-count }
   no; }
common {   on  node2   startup {
               wfc-timeout     3address 100.100.10.41:7789;
       } }proxy resourceon r0node2 {
       disk {                on-io-error detachinside 100.100.100.41:7790;
       }     outside 100.100.100.41:7791;
 net {      }
    } 
}

resource r2 protocol{
A;  startup {
           verify-alg crc32cwfc-timeout 3;
  }
  
	proxy {
      on-congestion pull-aheadmemlimit 500M;
  }
  
  net {
      sndbuf-sizeprotocol 10MA;
      verify-alg crc32c;
      on-congestion pull-fillahead; 80M;
      sndbuf-size 20M;
      pingcongestion-timeoutfill 30480M;
       }ping-timeout 30;
  }

  device e onminor pr12;
{  disk	e;
  meta-disk	g "C:/r2_meta.vhd";

  on node1 {
   device /dev/drbd0 node-id	1;    
  }
  on node2 {
   disk /dev/sdb1 node-id	2;
  }
  on node3 {
    node-id	3;
  address 200.200.23.132:7799;
 }
  
  connection DR-node1-node3 { 

	 host node1 address 100.100.100.9:6677 via proxy on node1 {
	 meta-disk internal	inside 100.100.100.9:6678;
	 	outside 100.100.100.9:6679;
	    }
	 host node3 address 100.100.100.11:6677 via proxy on pr2node3 {
	        	inside 100.100.100.11:6678;
	 	outside 100.100.100.11:6679;
	 }
  }

  device /dev/drbd0;
connection DR-node2-node3 { 

	 host node2 address 100.100.100.10:6680 via proxy on node2 {
	  disk /dev/sdb1;
               address 200.200.23.137:7799;
               meta-disk internal;
       }
}
resource r0_1{
       meta-disk internal;
	inside 100.100.100.10:6681;
	 	outside 100.100.100.10:6682;
	 }
	 host node3 address 100.100.100.11:6680 via proxy on node3 {
	 	inside 100.100.100.11:6681;
	 	outside 100.100.100.11:6682;
	 }
  }

  connection {
    host node1 address 10.20.25.9:6677;
    host node2 address 10.20.25.10:6677;
  }
}

global {
      device /dev/drbd10 disable-ip-verification;
       proxyusage-count     no;
}
common {
       startup {
      memlimit 500M;        }wfc-timeout     3;
  net {    }
}
resource r0 {
       protocoldisk {
A;               verifyon-io-algerror crc32cdetach;
       }
      on-congestion pull-ahead; net {
              sndbuf-sizeprotocol 10MA;
              congestionverify-fillalg 450Mcrc32c;
              pingon-timeoutcongestion 30pull-ahead; 
      }        stacked-on-top-of r0 {sndbuf-size 10M;
                address 10.30.0.135:7788congestion-fill 80M;
              ping-timeout proxy30;
on pr1 pr2{     }
       on pr1 {
        inside 10.30.0.135:7789;         device /dev/bsr0;
               outside 10.30.0.135:7790;	# mirror VIPdisk /dev/sdb1;
               address  }200.200.23.132:7799;
        }       meta-disk oninternal;
dd1 {      }
       on pr2 address 10.30.0.199:7788;{
               device proxy/dev/bsr0;
on dd1 {             disk /dev/sdb1;
         inside 10.30.0.199:7789;     address 200.200.23.137:7799;
               meta-disk internal;
       }
}
resource r0_1{
       outside 10.30.0.199:7790;meta-disk internal;
       device /dev/bsr10;
     #DR  mirrorproxy IP{
               }memlimit 500M;
       }
}

4.1.2. Dedicated server configuration

By default, configuration files are configured to the same for both nodes and DRX nodes. However, because of the nature of the dedicated server, it is necessary to modify the DRX config to match the drbd-utils installed on the dedicated server to accommodate all of these nodes in the DRX dedicated server. The configuration procedure is as described below and the configuration example is based on a Linux server.

       net {
              protocol A;
              verify-alg crc32c;
              on-congestion pull-ahead;
              sndbuf-size 10M;
              congestion-fill 450M;
              ping-timeout 30;

}

stacked-on-top-of r0 {

 address 10.

30.0.

135:

7788;

           proxy on 

pr1 pr2{
 

inside 10.30.0.135:7789;
       

 outside 

10.30.0.135:7790;	# mirror VIP
               

}

       }
 

      on dd1 

{
               

address 10.30.0.199:7788;
               proxy on dd1 {
 

inside 10.30.0.199:7789;
        

outside 10.30.0.199:7790;     #DR mirror IP
 

   }
       

}
}

Dedicated server configuration

By default, the configuration file is the same for both nodes and DRX nodes, but due to the nature of dedicated servers, DRX config must be modified to accommodate both Windows and Linux nodes in DRX. The configuration procedure is as described below, and the example configuration is based on a Linux dedicated server.

...

Number of threads to use when processing multi-thread packets.

※ It is intended for tuning and debugging, so it is not recommended to make any changes. 

drx.conf sample

resource r0 {
	device    d  minor 1;
	disk      d;
	meta-disk e;

	proxy {
		memlimit 1G;
	}	
		

	net {
		protocol A;
		on-congestion pull-ahead;
		congestion-fill 950M;
		ping-timeout 30;
	}

	on w12std-0 {
		node-id 0;
	}
	on w12std-1 {
		node-id 1;
	}

	connection win-r0 {
		host w12std-0  address 10.10.0.

77:

7789 via proxy on 74proxy1 {
			inside 10.10.0.115:7790;
			outside 

10.10.0.115:7791;
		}
		host w12std-1  address 10.10.0.203:7789 via proxy on 74proxy2 {
			inside 10.10.0.102:7790;
			outside 10.10.0.102:7791;
		}
	}

}

resource r0 {
             inside 10.10.0.102:7790;device /dev/bsr001; # dummy
        disk /dev/sdb1; # dummy
        meta-disk /dev/sdc1; # dummy

		proxy outside 10.10.0.102:7791;{
                memlimit }1G;
        }
  } 

resource r1 { 	device /dev/drbd001;
	disk /dev/sdb1;
	meta-disk /dev/sdc1;

	proxy {
		memlimit 1G;
	}
	net{
		 net{
                protocol A;
				on-congestion pull-ahead;
				congestion-fill 950M;
		
                ping-timeout 30;
	}  	 	on cen74-1 { 		node-id 0; 	}
	on
cen74-2 { 		node-id 1; 	}  	connection linux-r1 {
		host cen74-1 address 10.10.0.11:7792 via proxy on 74proxy1 {
			inside 10.10.0.115:7793;
			outside 10.10.0.115:7794;
		}
		host cen74-2 address 10.10.0.105:7792 via proxy on 74proxy2 {
			inside 10.10.0.102:7793;
			outside 10.10.0.102:7794;
		}
	}
}

resource r0 on w12std-0 {
                node-id 0;
        }
        on w12std-1 {
        device /dev/drbd001; # dummy     node-id 1;
   disk /dev/sdb1; # dummy  }
      meta-disk /dev/sdc1; #connection dummywin-r0 {
        proxy {       host w12std-0 address 10.10.0.77:7789 via proxy on 74proxy1 {
 memlimit 1G;         }         net{    inside 10.10.0.115:7790;
           protocol A; 				on-congestion pull-ahead; 				congestion-fill 950M;        outside 10.10.0.115:7791;
       ping-timeout 30;         }
         on w12std-0 {     host w12std-1           node-id 0;
        }
        on w12std-1address 10.10.0.203:7789 via proxy on 74proxy2 {
                node-id 1;       inside  }10.10.0.102:7790;
         connection win-r0 {                 host w12std-0 address outside 10.10.0.77102:77897791;
via proxy on 74proxy1 {            }
        }
}

resource r1 {
inside 10.10.0.115:7790;
                        outside 10.10.0.115:7791;
                }
                host w12std	device /dev/bsr001;
	disk /dev/sdb1;
	meta-disk /dev/sdc1;

	proxy {
		memlimit 1G;
	}
	net{
		protocol A;
		on-congestion pull-ahead;
		congestion-fill 950M;
		ping-timeout 30;
	}
	
	on cen74-1 {
		node-id 0;
	}
	on cen74-2 {
		node-id 1;
	}

	connection linux-r1 {
		host cen74-1 address 10.10.0.20311:77897792 via proxy on 74proxy274proxy1 {
                        			inside 10.10.0.115:7793;
			outside 10.10.0.115:7794;
		}
		host cen74-2 address 10.10.0.105:7792 via proxy on 74proxy2 {
			inside 10.10.0.102:77907793;
			outside 10.10.0.102:7794;
		}
	}
}

resource r0 {
        device /dev/bsr001; # dummy 
        outside 10.10.0.102:7791disk /dev/sdb1; # dummy
        meta-disk /dev/sdc1; # dummy

   }     proxy {
  } } 

resource r1 { 	device /dev/drbd001; 	disk /dev/sdb1; 	meta-disk /dev/sdc1;  	proxy { 		memlimit 1G;
	}
	net{
		        }
        net{
                protocol A;
				on-congestion pull-ahead;
				congestion-fill 950M;
		                ping-timeout 30;
 	}  	on cen74-1 { 		node-id 0; 	}
	on
cen74-2 { 		node-id 1; 	}    	connectionon linuxw12std-r10 {
 		host cen74-1 address 10.10.0.11:7792 via proxy on 74proxy1 { 			inside 10.10.0.115:7793; 			outside 10.10.0.115:7794; 		} 		host cen74node-2 address 10.10.0.105:7792 via proxy on 74proxy2 {
			inside 10.10.0.102:7793;
			outside 10.10.0.102:7794;
		}
	}
}

id 0;
        }
        on w12std-1 {
               

node-

id 

1;
 

}

 connection win-r0 {
                host w12std-0 

address 10.10.0.77:7789 via proxy on 74proxy1 {

                        inside 10.10.0.

115:7790;

                        outside 10.10.0.

115:7791;

}

      host w12std-1 

address 10.10.0.203:7789 via proxy on 74proxy2 {
      

inside 10.10.0.102:7790;
        

       outside 10.10.0.102:7791;
        

   }
        }
}

resource r1 {

	device /dev/bsr001;
	disk /dev/sdb1;
	meta-disk /dev/sdc1;

	proxy {
		memlimit 1G;
	}
	net{
		protocol A;

		on-congestion pull-ahead;
		congestion-fill 950M;
		ping-timeout 30;
	}

	on cen74-1 {

		node-id 0;

	}
	on cen74-2 {

		node-id 1;
	}

	connection linux-r1 

{
		host cen74-1 address 10.10.0.11:7792 via proxy on 74proxy1 {

			inside 10.10.0.115:7793;
			outside 10.10.0.115:7794;
		}
		host cen74-2 address 10.10.0.105:7792 via proxy on 74proxy2 {
			inside 

10.10.0.102:7793;
			outside 10.10.0.

102:7794;
		}
	}
}

resource r0 {
	device    d  minor 1;
	disk   

   d;
	meta-disk e;

	proxy {
		memlimit 1G;
	}	
	
	net {
		protocol A;

		on-congestion pull-ahead;
		congestion-fill 950M;
		ping-timeout 30;
	}

	on w12std-0 {
		node-id 0;
	}
	on w12std-1 {
		node-id 1;
	}

	connection win-r0 {
		host w12std-0  address 10.10.0.77:7789 via proxy on 74proxy1 {
			inside 10.10.0.

115:

7790;
			outside 10.10.0.115:7791;
		}
		host w12std-1  address 10.10.0.203:7789 via proxy on 74proxy2 {

			inside 10.10.0.102:

7790;
			outside 10.10.0.102:7791;

		}
	}

}

resource r1 {

        device /dev/

bsr0;
        disk /dev/sdb1;

        meta-disk /dev/sdc1;

proxy 

{
                memlimit 1G;
        }
        net{
                protocol A;
				on-congestion pull-ahead;
				congestion-fill 950M;

                ping-timeout 30;
 

     }
        on cen74-1 {

4.3. drx.conf

You can set the DRX internal properties independently of the DRBD configuration. Normally, you don't need to provide a property file because it works with the DRX preferences. This property is applied at the start of the DRX, and the DRX property file is created with reference to the following properties table.

• file name: "drx.conf"
• default path: DRX Installed path
• Caution: [global] section should be described at the beginning of the file

...

• Located in "base-dir/lang" of the configuration.
• ex) korean.ini

...

DRX install path

...

Default path where DRX is installed

...

Windows:

• ../etc/drbd.conf

Linux:

• /etc/drbd.conf

...

Timeout value in seconds used by socket connect or listen actions

...

Timeout value in seconds after connecting to a remote DRX, while sending and receiving initialization packets

...

Specify the log level that is written as a file

...

on: Allow only the IP connections set in dbd.conf.
off: Allow connections for all IPs.

...

Block size to be used for compression/encryption

• Note: The size of the transfer buffer for compression/encryption is set to twice the block-size value and is set to 1MB maximum.

                node-id 0;
        }
        on cen74-2 {
                node-id 1;
        }

        connection linux-r1 {
                host cen74-1 address 10.10.0.11:7792 via proxy on 74proxy1 {
                        inside 10.10.0.115:7793;
                        outside 10.10.0.115:7794;
                }
                host cen74-2 address 10.10.0.105:7792 via proxy on 74proxy2 {
                        inside 10.10.0.102:7793;
                        outside 10.10.0.102:7794;
                }
        }

resource r1 {
	device /dev/bsr0;
	disk /dev/sdb1;
	meta-disk /dev/sdc1;
	
	proxy {
		memlimit 1G;
	}
	net{
		protocol A;
		on-congestion pull-ahead;
		congestion-fill 950M;
		ping-timeout 30;
	}

	on cen74-1 {
		node-id 0;
	}
	on cen74-2 {
		node-id 1;
	}

	connection linux-r1 {
		host cen74-1 address 10.10.0.11:7792 via proxy on 74proxy1 {
			inside 10.10.0.115:7793;
			outside 10.10.0.115:7794;
		}
		host cen74-2 address 10.10.0.105:7792 via proxy on 74proxy2 {
			inside 10.10.0.102:7793;
			outside 10.10.0.102:7794;
		}
	}
}

drx.conf

Apart from the BSR configuration, you can set DRX internal behavior properties, which have the meaning of global settings that are applied when DRX starts. In most cases, you do not need to modify the drx.conf file, as DRX default settings will work. Use the following table of properties as a guide.

• file name: "drx.conf"
• default path: DRX Installed path
• Caution: [global] section should be described at the beginning of the file

drx.conf sample