From: "DERUMIER, Alexandre" <Alexandre.DERUMIER@groupe-cyllene.com>
To: Laurent GUERBY <laurent@guerby.net>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Dietmar Maurer <dietmar@proxmox.com>
Subject: Re: [pve-devel] qemu 7.0 : fleecing backup (aka: local temp write cache"
Date: Sun, 31 Jul 2022 18:24:18 +0000 [thread overview]
Message-ID: <5e9c0cd3-b006-8f32-b9fa-f054861d5214@groupe-cyllene.com> (raw)
In-Reply-To: <1659289657.6016.30.camel@guerby.net>
Le 31/07/22 à 19:47, Laurent GUERBY a écrit :
On Sun, 2022-07-31 at 16:49 +0000, DERUMIER, Alexandre wrote:
Le 31/07/22 à 18:19, Dietmar Maurer a écrit :
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.
Why don't you use a local(fast) PBS instance, then sync to the slow
remote?
Hi Dietmar.
Can I use a small local fast PBS instance without need to keep the
full
datastore chunks ?
I have 300TB nvme in production, I don't want to buy 300TB nvme for
backup.
I known that I can keep more retentions on remote storage slow, but
what
about the local fast pbs ?
Hi Alexandre,
I had the exact same issue:
https://antiphishing.cetsi.fr/proxy/v3?i=SGI0YVJGNmxZNE90Z2thMFYLWSxJOfIERJocpmb73Vs&r=SW5LV3JodE9QZkRVZ3JEYYKpfBJeBDlAX9EWSgcxKTOskC-MKbYiKWCY7M6ocEtDq8CeXBnAzGsMk-U5K5P6Yg&f=bnJjU3hQT3pQSmNQZVE3aO0r-ZB14cskqerzYUDW5Vk-5C50pA9QKkzP7UNmmVTG&u=https%3A//forum.proxmox.com/threads/partial-sync-job-pre-prune.106441/&k=dFBm
Here is the bugzilla:
https://antiphishing.cetsi.fr/proxy/v3?i=SGI0YVJGNmxZNE90Z2thMFYLWSxJOfIERJocpmb73Vs&r=SW5LV3JodE9QZkRVZ3JEYYKpfBJeBDlAX9EWSgcxKTOskC-MKbYiKWCY7M6ocEtDq8CeXBnAzGsMk-U5K5P6Yg&f=bnJjU3hQT3pQSmNQZVE3aO0r-ZB14cskqerzYUDW5Vk-5C50pA9QKkzP7UNmmVTG&u=https%3A//bugzilla.proxmox.com/show_bug.cgi%3Fid%3D3701&k=dFBm
So no AFAIK there's no way to do a partial sync. A tool to sync a
specific backup (instead of a group) and a bit of scripting would do
the job.
Sincerely,
Laurent
Hi Laurent !
I think that my need is a little bit different.
looking at your forum message
"have it sync to our current existing primary PBS server (SSD). The NVME server will have less space than the SSD server and not enough space to have a copy of all backups of the primary,"
I think It's not the same. I need the inverse. My primary storage need to be fast and small, and secondary synced remote is big && slow.
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com<mailto:pve-devel@lists.proxmox.com>
https://antiphishing.cetsi.fr/proxy/v3?i=SGI0YVJGNmxZNE90Z2thMFYLWSxJOfIERJocpmb73Vs&r=SW5LV3JodE9QZkRVZ3JEYYKpfBJeBDlAX9EWSgcxKTOskC-MKbYiKWCY7M6ocEtDq8CeXBnAzGsMk-U5K5P6Yg&f=bnJjU3hQT3pQSmNQZVE3aO0r-ZB14cskqerzYUDW5Vk-5C50pA9QKkzP7UNmmVTG&u=https%3A//lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel&k=dFBm
next prev parent reply other threads:[~2022-07-31 18:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2022-08-01 8:10 ` DERUMIER, Alexandre
-- strict thread matches above, loose matches on Subject: below --
2022-08-01 8:31 Dietmar Maurer
2022-08-01 14:36 ` DERUMIER, Alexandre
2022-07-31 15:58 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=5e9c0cd3-b006-8f32-b9fa-f054861d5214@groupe-cyllene.com \
--to=alexandre.derumier@groupe-cyllene.com \
--cc=dietmar@proxmox.com \
--cc=laurent@guerby.net \
--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