From: Ray Morris <support@bettercgi.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] efficiently copying snapshot data.
Date: Fri, 09 Jul 2010 20:14:11 -0500 [thread overview]
Message-ID: <1278724451.8612.38@raydesk1.bettercgi.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1007092051070.29512@bmsred.bmsi.com> (from stuart@bmsi.com on Fri Jul 9 20:01:02 2010)
> > rsync/
> That doesn't do what he wants. He wants to copy only
> the COW blocks.
The COW blocks being those that are different between the
master and the snapshot, correct? Have I been doing it wrong
all of these years, because I was under the distinct impression
that rsync copied only the differences.
Perhaps the confusion is here is whether he wants the destination
to include nothing but the changed the blocks, but that doesn't
require any new LVM programming. If you want the destination to be
a snapshot, only the differences, just take a snapshot on the
new machine and rsync from the old snapshot to the new snapshot.
A very few blocks might get duplicated because of file level versus
block level, but in practice that hasn't seemed to be significant.
At least, not for our 160 or so VMs.
--
Ray Morris
support@bettercgi.com
Strongbox - The next generation in site security:
http://www.bettercgi.com/strongbox/
Throttlebox - Intelligent Bandwidth Control
http://www.bettercgi.com/throttlebox/
Strongbox / Throttlebox affiliate program:
http://www.bettercgi.com/affiliates/user/register.php
next prev parent reply other threads:[~2010-07-10 1:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-09 23:47 [linux-lvm] efficiently copying snapshot data Michael Closson
2010-07-10 0:38 ` Ray Morris
2010-07-10 1:01 ` Stuart D. Gathman
2010-07-10 1:14 ` Ray Morris [this message]
2010-07-10 15:50 ` Alasdair G Kergon
2010-07-12 21:25 ` Michael Closson
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=1278724451.8612.38@raydesk1.bettercgi.com \
--to=support@bettercgi.com \
--cc=linux-lvm@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.