'drbd' is a block device for building high-availability clusters. DRBD takes over the data, writes it to the local disk and sends it to the other host. On the other host, it takes it to the disk there. The other components needed are a cluster membership service, which is supposed to be heartbeat, and an application that works on top of a block device (ie, a filesystem and fsck). Each device has either a 'primary' or 'secondary' state. The application should run and access the device on the node with the primary device. Every write is sent to the local 'lower level block device' and to the node with the device in 'secondary' state. The secondary device then writes the data to its lower level block device. If the primary node fails, heartbeat is switching the secondary device into primary state and starts the application there. If the failed node comes up again, it is a new secondary node and will synchronise its content to the primary node whithout interruption of service in the background. Only those parts of the device that actually have been changed will resync.
released on 1 February 2005
|License||Verified by||Verified on||Notes|
|GPLv2orlater||Janet Casey||2 February 2005|
Leaders and contributors
Resources and communication
This entry (in part or in whole) was last reviewed on 7 January 2008.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the page “GNU Free Documentation License”.
The copyright and license notices on this page only apply to the text on this page. Any software or copyright-licenses or other similar notices described in this text has its own copyright notice and license, which can usually be found in the distribution or license text itself.