From: Kashyap Chamarthy <kchamart@redhat.com>
To: Bharadwaj Rayala <bharadwaj.rayala@rubrik.com>
Cc: qemu-discuss@nongnu.org, qemu-devel@nongnu.org,
Suman Swaroop <suman.swaroop@rubrik.com>,
kashyap.cv@gmail.com
Subject: Re: [Qemu-devel] Incremental drive-backup with dirty bitmaps
Date: Thu, 24 Jan 2019 09:57:43 +0100 [thread overview]
Message-ID: <20190124085743.GE23279@paraplu> (raw)
In-Reply-To: <CAMAMwPB1GJNxsgcvZLHwHuLp-AjuWtnYCGOm6+U4DwdLsNrU8A@mail.gmail.com>
On Wed, Jan 23, 2019 at 12:59:27AM +0530, Bharadwaj Rayala wrote:
[...]
Eric has responded with excellent detail, as usual; a "meta question"
below.
> I am trying to build a backup workflow(program) using drive-backup along
> with dirty bitmaps to take backups of kvm vms.
Is this program that you're building just specific to your environment?
Or is it a generic open source project (or proprietary product)?
> EIther pull/push model works for me. Since drive-backup push model is
> already implemented, I am going forward with it. I am not able to
> figure out a few details and couldn't find any documentation around
> it. Any help would be appreciated
[...]
--
/kashyap
prev parent reply other threads:[~2019-01-24 9:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 19:29 [Qemu-devel] Incremental drive-backup with dirty bitmaps Bharadwaj Rayala
2019-01-22 21:54 ` Eric Blake
2019-01-23 18:08 ` Bharadwaj Rayala
2019-01-23 19:09 ` Eric Blake
2019-01-24 9:16 ` Kashyap Chamarthy
[not found] ` <CAMAMwPA_H77fnC+dOzBt+nRQ+=oPHtpw2DRYMCEtnGdo1OU0Hw@mail.gmail.com>
2019-02-06 17:20 ` Suman Swaroop
2019-02-06 17:57 ` Eric Blake
2019-01-24 8:57 ` Kashyap Chamarthy [this message]
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=20190124085743.GE23279@paraplu \
--to=kchamart@redhat.com \
--cc=bharadwaj.rayala@rubrik.com \
--cc=kashyap.cv@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-discuss@nongnu.org \
--cc=suman.swaroop@rubrik.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).