From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>,
Bernhard Dick <bernhard@bdick.de>
Subject: Re: [PVE-User] Backup broken?
Date: Sun, 1 Nov 2020 20:48:41 +0100 [thread overview]
Message-ID: <9c16c66e-6a83-4da9-84e8-28efa0ff7c3a@proxmox.com> (raw)
In-Reply-To: <746ccce3-578f-c75d-8958-f3776b7f1166@bdick.de>
On 01.11.20 14:14, Bernhard Dick wrote:
> I can even reproduce this behaviour by triggering the global Backup job from the web console. If I backup single VMs/Containers from the Host part of the web console it runs fine, however the global job removes also those backups when it is running.
Yes, there was a regression with this when adopting the newer prune "keep-daily",
"keep-weekly", ... logic. It acts quite different internally, but the storage
special case for maxfiles==0 was handled rather implicit, thus this did not
rang any alarm bells. I transformed it to a more explicit logic and we'll
add some more extensive test for this special case, so that it won't happen again.
The fix is packaged in pve-manager version 6.2-15, currently available on pvetest.
You can either add the pvetest repository[0], do `apt update && apt install pve-manager`,
then drop the test repo again, or manually download and install it, with using
`apt install` this still checks if the package is valid (i.e., signed by a trusted
key):
# wget http://download.proxmox.com/debian/pve/dists/buster/pvetest/binary-amd64/pve-manager_6.2-15_amd64.deb
# apt install ./pve-manager_6.2-15_amd64.deb
thanks for your report!
regards,
Thomas
[0]: https://pve.proxmox.com/wiki/Package_Repositories
next prev parent reply other threads:[~2020-11-01 19:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-31 14:11 Bernhard Dick
2020-11-01 12:48 ` Thomas Lamprecht
2020-11-01 13:14 ` Bernhard Dick
2020-11-01 19:48 ` Thomas Lamprecht [this message]
2020-11-01 20:17 ` Thomas Lamprecht
2020-11-02 9:17 ` Bernhard Dick
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=9c16c66e-6a83-4da9-84e8-28efa0ff7c3a@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=bernhard@bdick.de \
--cc=pve-user@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