All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christophe Varoqui <christophe.varoqui@free.fr>
To: Jonathan Brassow <jbrassow@redhat.com>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: [RFC] dm snapshot based asynchronous replication
Date: Wed, 22 Apr 2009 23:20:18 +0200	[thread overview]
Message-ID: <1240435218.492.29.camel@plop> (raw)
In-Reply-To: <540AD48B-A810-4F15-BEA0-5879350EA893@redhat.com>


> It also seems that the script is not generic enough to handle the  
> variety of exception stores that are coming.  I just wrote a 'snapshot- 
> merge' target that will do what you ask.  I will post the patch  
> shortly.  However, this won't help you in RHEL5.
> 
Jonathan,

thank you for this new snapshot-merge target. This plus the shared
exception patches will certainly bring the definitive answer for
LVM2-based replication/backup/time-navigation needs for RHEL6. I hope
btrfs will even bring to the table an interesting alternative sometime
in the el6 lifecycle.

But for those stuck with (entitlements on thousands of) el4 and el5
deployments, here is my contribution to the poor-man's async
replication :

http://christophe.varoqui.free.fr/rcow/

* rcow.pl
parse a cow device to generate a delta-file of 2 snapshots

* rcowd
handles full sync of remote device and schedule (one-shot or loop) :
- delta-file creation
- snapshot rotation
- delta-file sending to remote
- delta-file load on remote


Todo:
- more error checking
- sequencing cookies :
  o store on remote the last delta-file cookie succesfully loaded
  o store {prev_cookie, this_cookie} in delta_files
  o verify on remote that delta-file(prev_cookie)==last applied cookie
- replace the dd plumbing, though the readability of delta-file +
command-file is quite nice for understanding what happen (and may go
wrong). May be port to C.
- delta-file historization and rotation


Comments and contributions welcome.

Regards,
cvaroqui

  reply	other threads:[~2009-04-22 21:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <137413921.2150341239820262767.JavaMail.root@zimbra16-e3.priv.proxad.net>
2009-04-15 18:31 ` [RFC] dm snapshot based asynchronous replication christophe.varoqui
2009-04-16  7:02   ` Lars Ellenberg
2009-04-17 18:01     ` Jonathan Brassow
2009-04-22 21:20       ` Christophe Varoqui [this message]
     [not found] <1567864196.1766411239656669717.JavaMail.root@zimbra16-e3.priv.proxad.net>
2009-04-13 21:08 ` christophe.varoqui
2009-04-14  3:29   ` FUJITA Tomonori
2009-04-14 14:27     ` Jonathan Brassow
2009-04-14 23:09     ` christophe.varoqui

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1240435218.492.29.camel@plop \
    --to=christophe.varoqui@free.fr \
    --cc=dm-devel@redhat.com \
    --cc=jbrassow@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.