From: "DERUMIER, Alexandre" <Alexandre.DERUMIER@groupe-cyllene.com>
To: pve-devel <pve-devel@lists.proxmox.com>
Subject: [pve-devel] qemu 7.0 : fleecing backup (aka: local temp write cache"
Date: Sun, 31 Jul 2022 15:58:26 +0000 [thread overview]
Message-ID: <8e03a831-a1fe-73f0-c720-9a0b0f8d8b48@groupe-cyllene.com> (raw)
Hi,
Currently, proxmox backup are using copy-before-write to have snapshot
backup.
This works great until you have a slow or remote storage with higher
latencies than the vm storage.
This can slowdown a lot the vm is a lot of writes occur when backup is
running. (or even can hang the vm if backup storage goes down during the
backup)
qemu backup support since 1-2 years some kind of local write cache,
called "fleecing".
When backup is running, if a block is not yet backuped, it's going to a
temp local disk image.
Some improvements have been made in qemu 7.0, previously only qcow2 was
allowed for the temp disk, now it's working with any disk
https://github.com/qemu/qemu/commit/af5bcd775f3115e4c1b7715920a67b31b119de30
Could it be possible to implement same king of cache for proxmox backup ?
I think qemu implementation is a simple block filter (It's even possible
to expose a virtual snasphot), so maybe it could be easy to implement it ?
This is really a blocker for me,I can't use pbs because I'm using nvme
is production, and a 7200k hdd backup in a remote 200km site with 5ms
latency.
If I could use temp nvme cache on the hypervisor, it could be wonderfull :)
I had opened a bugzilla some week ago with same kind of local cache idea
(didn't known about qemu fleecing at this time, seem the way to go)
https://bugzilla.proxmox.com/show_bug.cgi?id=4136
next reply other threads:[~2022-07-31 15:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-31 15:58 DERUMIER, Alexandre [this message]
2022-07-31 16:19 Dietmar Maurer
2022-07-31 16:49 ` DERUMIER, Alexandre
2022-07-31 17:47 ` Laurent GUERBY
2022-07-31 18:24 ` DERUMIER, Alexandre
2022-08-01 8:10 ` DERUMIER, Alexandre
2022-08-01 8:31 Dietmar Maurer
2022-08-01 14:36 ` DERUMIER, Alexandre
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=8e03a831-a1fe-73f0-c720-9a0b0f8d8b48@groupe-cyllene.com \
--to=alexandre.derumier@groupe-cyllene.com \
--cc=pve-devel@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox