• May be used to add redundancy to existing deployments
  • Fully synchronous, memory synchronous or asynchronous modes of operation
  • Masking of local IO errors
  • Shared secret to authenticate the peer upon connect
  • Bandwidth of background resynchronization tunable
  • Automatic recovery after node, network, or disk failures
  • Efficient resynchronization, only blocks that were modified during the outage of a node.
  • Short resynchronization time after the crash of an active node, independent of the device size.
  • Automatic detection of the most up-to-date data after complete failure
  • Integration scripts for use with Heartbeat
  • Dual primary support for use with GFS/OCFS2
  • Configurable handler scripts for various DRBD events
  • Online data verification
  • Optional data digests to verify the data transfer over the network
  • Integration scripts for use with Xen
  • Usable on LVM's logical volumes. Usable as physical volume for LVM
  • Integration scripts for LVM to automatically take a snapshot before a node becomes the target of a resynchronization
  • Dependencies to serialize resynchronization, in case of default all devices in parallel
  • Heartbeat integration to outdate peers with broken replication links, avoids switchovers to stale data
  • Many tuning parameters allow to optimize DRBD for specific machines, networking hardware, and storage subsystem
  • Integration scripts for use with RedHat Cluster (excl. the GUI tools)
  • Existing file systems can be integrated into new DRBD setups without the need of copying
  • Support for a third, off-site node for disaster recovery (since 8.3)
  • Support for compression of the bitmap exchange (since 8.3.2, keyword: use-rle)
  • Support for floating peers (since 8.3.2) in drbdadm
  • Feature complete OCF Heartbeat/Pacemeker resource agent (since 8.3.2)
  • Resource level fencing script, using Pacemaker's constraints (since 8.3.2)
  • Supports TCP/IP over Ethernet, SuperSockets over Dolphin NICs (8.3.2) and SDP over Infiniband (8.3.3)
  • Supports single block device sizes of up to one petabyte (since 8.3.10)
  • Supports active bandwidth management for mirroring over long distance and high throughput internet links. Including optional complete fall behind in case bandwidth is not sufficient. (since 8.3.10)
  • Supports replication of multiple volumes (block devices) via a single network connection
  • Optional load balancing of read requests

Optionally available

These features are commercially available through → LINBIT®.

  • DRBD® Proxy. Improves performance for asynchronous mirroring over long distance links by buffering data. The buffering of data is only limited by the physical RAM of the machine running the proxy. Optionally compresses the data.
  • Professional Consulting and Support in various flavours to fit your needs.


While these topics are not features of DRBD they may be of interest for deployment.

  • Transfer between DRBD nodes can be secured using standard OS means like IPSec or OpenVPN.
  • Standard OS block device encryption can be used on top of DRBD devices.
  • A DRBD device might be used as a PV for LVM

→ Continue with Releases

© 2008-2015: LINBIT HA-Solutions GmbH : Stiegergasse 18, 1150 Vienna, Austria : phone +43 1 817 82 92 - 0 : office@linbit.com

LINBIT USA, LLC, 3720 SW 141st Ave. Suite 100, Beaverton, OR 97005, USA