I’ve been looking at various storage options recently. DRBD is pretty cool:

And, of course, we only will resynchronize those parts of the device that actually have been changed. DRBD has always done intelligent resynchronization when possible. Starting with the DBRD-0.7 series, you can define an “active set” of a certain size. This makes it possible to have a total resync time of 1–3 min, regardless of device size (currently up to 4TB), even after a hard crash of an active node.

DRBD is a network block level intelligent replication protocol. It syncs local disk blocks on two separate nodes and smartly manages dirty blocks while out of communication. Normally this is used for Active/Passive or Active/Active cluster HA. It could also provide a method for off site replication.

Run a storage server with iSCSI or AoE targets on LVM devices over the DRDb block device, with the secondary node on a remote server via a vpn. Specific details about this setup are discussed in Disaster Recovery with “Tele-DRBD” on the Linux HA Wiki. Some details on LVM over DRBD. Also worth checking the NFS on DRBD page.

Technorati Tags: , , ,

Comments are closed.