From: "Radosław Korzeniewski" <radoslaw@korzeniewski.net>
To: Stefan Reiter <s.reiter@proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] VM Incremental backup for 3-party solution (Qemu)
Date: Tue, 24 Aug 2021 12:58:12 +0200 [thread overview]
Message-ID: <CAF_EmoDDSNdiLm-ktF2nUZSxnmaQ9oqn5FnxuvxA1bt7cM5qHQ@mail.gmail.com> (raw)
In-Reply-To: <6bd6cbed-5519-cb7e-628c-13e934639652@proxmox.com>
Hello,
czw., 19 sie 2021 o 16:22 Stefan Reiter <s.reiter@proxmox.com> napisał(a):
> But more importantly, 'drive-backup' and the bitmap support around that
>
are not based on our code, they are from upstream QEMU. We implement the
> 'backup' and 'query-backup' QMP calls.
>
So, did you "change" the upstream feature when implementing your own?
> There's nothing against using the native calls if they fit your use case,
> but for support it would make more sense to contact upstream and read
> through their documentation :)
>
Thanks for the tips. I already read the Qemu documentation and I'm able to
make a successful full + incr backup using a "stock" Qemu with my
procedure. So I assume the procedure is fine.
Then I decided to ask a question here as it is not working with Proxmox, so
I suspect that something changed between upstream and Proxmox distributions.
I'm not a Proxmox developer, so finding what is not working on Qemu
hypervisor is hard.
Back to my main question: Do you have any idea why the job fell into a
paused state and how I should proceed?
--
Radosław Korzeniewski
radoslaw@korzeniewski.net
prev parent reply other threads:[~2021-08-24 10:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 13:21 Radosław Korzeniewski
2021-08-19 14:22 ` Stefan Reiter
2021-08-24 10:58 ` Radosław Korzeniewski [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=CAF_EmoDDSNdiLm-ktF2nUZSxnmaQ9oqn5FnxuvxA1bt7cM5qHQ@mail.gmail.com \
--to=radoslaw@korzeniewski.net \
--cc=pve-devel@lists.proxmox.com \
--cc=s.reiter@proxmox.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.