From: John Snow <jsnow@redhat.com>
To: Qemu-block <qemu-block@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>
Cc: Markus Armbruster <armbru@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-block] [RFC] Differential Backups
Date: Tue, 05 May 2015 11:55:49 -0400 [thread overview]
Message-ID: <5548E805.7090304@redhat.com> (raw)
In-Reply-To: <20150505102546.GB3149@stefanha-thinkpad.redhat.com>
On 05/05/2015 06:25 AM, Stefan Hajnoczi wrote:
> On Wed, Apr 29, 2015 at 06:51:08PM -0400, John Snow wrote:
>> This is a feature that should be very easy to add on top of the existing
>> incremental feature, since it's just a difference in how the bitmap is
>> treated:
>>
>> Incremental
>> - Links to the last incremental (managed by libvirt)
>> - Clears the bitmap after creation
>>
>> Differential:
>> - Links to the last full backup always (managed by libvirt)
>> - Does not clear the bitmap after creation
>>
>> No biggie.
>
> Differential backups can be done using incremental backup functionality
> in QEMU:
>
> The client application points QEMU to the same target repeatedly instead
> of keeping separate incremental backups.
>
> Stefan
>
Oh, so you're saying:
[anchor]<--[diff1]
And then when making a new incremental, we re-use diff1 as a target and
overwrite it so that it becomes:
[anchor]<--[diff2]
In effect giving us a differential.
OK, so it's possible, but we still lose out on some flexibility that a
slightly different mode would provide us, like the ability to keep
multiple differentials if desired. (Well, I suppose we *can* create
those by manually copying differentials after we create them, but that
seems hackier than necessary.)
Still, it would be such a paltry few lines of code and introduce no real
complexity to the subsystem, and it might make libvirt's time a little
easier for managing such things.
--js
next prev parent reply other threads:[~2015-05-05 15:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-29 22:51 [Qemu-devel] [RFC] Differential Backups John Snow
2015-05-05 10:25 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2015-05-05 15:55 ` John Snow [this message]
2015-05-06 9:17 ` Stefan Hajnoczi
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=5548E805.7090304@redhat.com \
--to=jsnow@redhat.com \
--cc=armbru@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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.