diff options
| author | Shriram Rajagopalan <rshriram@cs.ubc.ca> | 2011-05-26 15:03:39 +0100 |
|---|---|---|
| committer | Shriram Rajagopalan <rshriram@cs.ubc.ca> | 2011-05-26 15:03:39 +0100 |
| commit | b3f1e4ac567c2a03979a10991dd301d6c80b96e9 (patch) | |
| tree | 2ba8ec2a407eb4d80c3e3a997219e0368ad7b8f5 /tools/blktap2 | |
| parent | eadf449efd7518d8f5789c90aaa93c487b88fb98 (diff) | |
| download | xen-b3f1e4ac567c2a03979a10991dd301d6c80b96e9.tar.gz xen-b3f1e4ac567c2a03979a10991dd301d6c80b96e9.tar.bz2 xen-b3f1e4ac567c2a03979a10991dd301d6c80b96e9.zip | |
tools: remus: support DRBD disk backends
DRBD disk backends can be used instead of tapdisk backends for Remus.
This requires a Remus style disk replication protocol (asynchronous
replication with output buffering at backup), that is not available in
standard DRBD code. A modified version that supports this new replication
protocol is available from git://aramis.nss.cs.ubc.ca/drbd-8.3-remus
Use of DRBD disk backends provides a means for efficient
resynchronization of data after the crashed machine comes back
online. Since DRBD allows for online resynchronization, a DRBD backed
Remus VM does not have to be stopped or shutdown while the disks are
resynchronizing. Once resynchronization is complete, Remus can be
started at will.
Signed-off-by: Shriram Rajagopalan <rshriram@cs.ubc.ca>
Committed-by: Ian Jackson <ian.jackson@eu.citrix.com>
Diffstat (limited to 'tools/blktap2')
0 files changed, 0 insertions, 0 deletions