All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH v6 0/4] dm-replicator: introduce new remote replication target
@ 2009-12-18 15:44 heinzm
  2009-12-18 15:44 ` [PATCH v6 1/4] dm-replicator: documentation and module registry heinzm
  0 siblings, 1 reply; 9+ messages in thread
From: heinzm @ 2009-12-18 15:44 UTC (permalink / raw)
  To: dm-devel; +Cc: Heinz Mauelshagen

From: Heinz Mauelshagen <heinzm@redhat.com>


* 6th version of patch series (initial version dated Oct 23 2009) *

Rebased to 2.6.33-rc1 (dm-dirty-log interface change).
Fixed some sparse warnings spotted by Alasdair (make C=1).


This is a series of 4 patches introducing the device-mapper remote
data replication target "dm-replicator" to kernel 2.6.

Userspace support for remote data replication will be in
a future LVM2 version.

The target supports disaster recovery by replicating groups of active
mapped devices (ie. receiving io from applications) to one or more
remote sites to paired groups of equally sized passive block devices
(ie. no application access). Synchronous, asynchronous replication
(with fallbehind settings) and temporary downtime of transports
are supported.

It utilizes a replication log to ensure write ordering fidelity for
the whole group of replicated devices, hence allowing for consistent
recovery after failover of arbitrary applications
(eg. DBMS utilizing N > 1 devices).

In case the replication log runs full, it is capable to fall back
to dirty logging utilizing the existing dm-log module, hence keeping
track of regions of devices wich need resynchronization after access
to the transport returned.

Access logic of the replication log and the site links are implemented
as loadable modules, hence allowing for future implementations with
different capabilities in terms of additional plugins.

A "ringbuffer" replication log module implements a circular ring buffer
store for all writes being processed. Other replication log handlers
may follow this one as plugins too.

A "blockdev" site link module implements block devices access to all remote
devices, ie. all devices exposed via the Linux block device layer
(eg. iSCSI, FC).
Again, other eg. network type transport site link handlers may
follow as plugins.

Please review for upstream inclusion.

Heinz

^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, other threads:[~2011-07-18  9:44 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-12-18 15:44 [PATCH v6 0/4] dm-replicator: introduce new remote replication target heinzm
2009-12-18 15:44 ` [PATCH v6 1/4] dm-replicator: documentation and module registry heinzm
2009-12-18 15:44   ` [PATCH v6 2/4] dm-replicator: replication log and site link handler interfaces and main replicator module heinzm
2009-12-18 15:44     ` [PATCH v6 3/4] dm-replicator: ringbuffer replication log handler heinzm
2009-12-18 15:44       ` [PATCH v6 4/4] dm-replicator: blockdev site link handler heinzm
2011-07-18  9:44       ` [PATCH v6 3/4] dm-replicator: ringbuffer replication log handler Busby
2010-01-07 10:18   ` [PATCH v6 1/4] dm-replicator: documentation and module registry 张宇
2010-01-08 19:44     ` Heinz Mauelshagen
2010-02-09  1:48       ` Busby

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.