- 2.1 Configuring the DRBD Environment
- 2.1.1 Setting Up Your Operating System for DRBD
- 2.1.2 Installing and Configuring DRBD
- 2.1.3 Setting Up a DRBD Primary Node
- 2.1.4 Setting Up a DRBD Secondary Node
- 2.1.5 Monitoring DRBD Device
- 2.1.6 Managing your DRBD Installation
- 2.1.7 Additional DRBD Configuration Options
Additional options you may want to configure:
-
protocol— specifies the level of consistency to be used when information is written to the block device. The option is similar in principle to theinnodb_flush_log_at_trx_commitoption within MySQL. Three levels are supported:A— data is considered written when the information reaches the TCP send buffer and the local physical disk. There is no guarantee that the data has been written to the remote server or the remote physical disk.B— data is considered written when the data has reached the local disk and the remote node's network buffer. The data has reached the remote server, but there is no guarantee it has reached the remote server's physical disk.C— data is considered written when the data has reached the local disk and the remote node's physical disk.
The preferred and recommended protocol is C, as it is the only protocol which ensures the consistency of the local and remote physical storage.
-
size— if you do not want to use the entire partition space with your DRBD block device then you can specify the size of the DRBD device to be created. The size specification can include a quantifier. For example, to set the maximum size of the DRBD partition to 1GB you would use:size 1G;
With the configuration file suitably configured and ready to use, you now need to populate the lower-level device with the metadata information, and then start the DRBD service.
