From: "Richard W.M. Jones" <rjones@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>, Fam Zheng <famz@redhat.com>,
qemu-devel@nongnu.org, xiawenc@linux.vnet.ibm.com,
imain@redhat.com, Paolo Bonzini <pbonzini@redhat.com>,
dietmar@proxmox.com
Subject: Re: [Qemu-devel] [PATCH v4 0/8] block: drive-backup live backup command
Date: Sun, 19 May 2013 17:47:55 +0100 [thread overview]
Message-ID: <20130519164755.GA18311@redhat.com> (raw)
In-Reply-To: <1368693379-8434-1-git-send-email-stefanha@redhat.com>
On Thu, May 16, 2013 at 10:36:11AM +0200, Stefan Hajnoczi wrote:
[...]
> How can drive-backup be used?
> -----------------------------
> The simplest use-case is to copy a point-in-time snapshot to a local file.
>
> More advanced users may wish to make the target an NBD URL. The NBD server
> listening on the other side can process the backup writes any way it wishes. I
> previously posted an RFC series with a backup server that streamed Dietmar's
> VMA backup archive format.
I'm guessing the answer is no, but thought I would ask: Is there
any way to use this to do point-in-time inspection of guests?
AFAICT the only way to do it would be to make a complete copy of a
guest disk in another file.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top
next prev parent reply other threads:[~2013-05-19 16:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-16 8:36 [Qemu-devel] [PATCH v4 0/8] block: drive-backup live backup command Stefan Hajnoczi
2013-05-16 8:36 ` [Qemu-devel] [PATCH v4 1/8] block: add bdrv_add_before_write_notifier() Stefan Hajnoczi
2013-05-16 8:36 ` [Qemu-devel] [PATCH v4 2/8] block: add basic backup support to block driver Stefan Hajnoczi
2013-05-22 9:38 ` Kevin Wolf
2013-05-22 9:54 ` Paolo Bonzini
2013-05-22 9:56 ` Kevin Wolf
2013-05-22 13:58 ` Stefan Hajnoczi
2013-05-22 14:08 ` Kevin Wolf
2013-05-16 8:36 ` [Qemu-devel] [PATCH v4 3/8] block: add drive-backup QMP command Stefan Hajnoczi
2013-05-16 19:11 ` Eric Blake
2013-05-22 9:53 ` Kevin Wolf
2013-05-22 14:33 ` Stefan Hajnoczi
2013-05-16 8:36 ` [Qemu-devel] [PATCH v4 4/8] qemu-iotests: add 055 drive-backup test case Stefan Hajnoczi
2013-05-22 11:19 ` Kevin Wolf
2013-05-22 14:34 ` Stefan Hajnoczi
2013-05-16 8:36 ` [Qemu-devel] [PATCH v4 5/8] blockdev: rename BlkTransactionStates to singular Stefan Hajnoczi
2013-05-16 8:36 ` [Qemu-devel] [PATCH v4 6/8] blockdev: add DriveBackup transaction Stefan Hajnoczi
2013-05-16 19:21 ` Eric Blake
2013-05-17 7:02 ` Stefan Hajnoczi
2013-05-16 8:36 ` [Qemu-devel] [PATCH v4 7/8] blockdev: add Abort transaction Stefan Hajnoczi
2013-05-16 19:23 ` Eric Blake
2013-05-16 8:36 ` [Qemu-devel] [PATCH v4 8/8] qemu-iotests: test 'drive-backup' transaction in 055 Stefan Hajnoczi
2013-05-19 16:47 ` Richard W.M. Jones [this message]
2013-05-19 19:30 ` [Qemu-devel] [PATCH v4 0/8] block: drive-backup live backup command Paolo Bonzini
2013-05-19 19:41 ` Richard W.M. Jones
2013-05-22 11:23 ` Kevin Wolf
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=20130519164755.GA18311@redhat.com \
--to=rjones@redhat.com \
--cc=dietmar@proxmox.com \
--cc=famz@redhat.com \
--cc=imain@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=xiawenc@linux.vnet.ibm.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.