From: Bernhard Dick <bernhard@bdick.de>
To: pve-user@lists.proxmox.com
Subject: [PVE-User] Backup broken?
Date: Sat, 31 Oct 2020 15:11:48 +0100 [thread overview]
Message-ID: <1bea39e7-d656-d809-0774-baa935479f53@bdick.de> (raw)
Hi,
I've a weekly backup job on my proxmox (community version 6.2)
infrastructure. Yesterday I've updated to the latest package versions
available and in the night the backup job ran. But he decided to first
create a backup and then delete _all_ backups being on the backup
location which is now empty besides some log files.
Here is an excerpt of one of the mailed logs:
101: 2020-10-31 02:04:31 INFO: creating vzdump archive
'/mnt/pve/backup-fsn0/dump/vzdump-lxc-101-2020_10_31-02_04_30.tar.lzo'
101: 2020-10-31 02:05:15 INFO: Total bytes written: 838041600 (800MiB,
19MiB/s)
101: 2020-10-31 02:05:16 INFO: archive file size: 383MB
101: 2020-10-31 02:05:16 INFO: removing backup
'backup-fsn0:backup/vzdump-lxc-101-2020_10_14-00_57_00.tar.zst'
101: 2020-10-31 02:05:16 INFO: removing backup
'backup-fsn0:backup/vzdump-lxc-101-2020_10_16-19_20_41.tar.lzo'
101: 2020-10-31 02:05:16 INFO: removing backup
'backup-fsn0:backup/vzdump-lxc-101-2020_10_17-02_10_31.tar.lzo'
101: 2020-10-31 02:05:17 INFO: removing backup
'backup-fsn0:backup/vzdump-lxc-101-2020_10_24-02_03_29.tar.lzo'
101: 2020-10-31 02:05:25 INFO: removing backup
'backup-fsn0:backup/vzdump-lxc-101-2020_10_31-02_04_30.tar.lzo'
101: 2020-10-31 02:05:25 INFO: remove vzdump snapshot
101: 2020-10-31 02:05:26 INFO: Finished Backup of VM 101 (00:00:56)
Is it possible that I've triggert a very evil bug here?
Best regards
Bernhard
next reply other threads:[~2020-10-31 14:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-31 14:11 Bernhard Dick [this message]
2020-11-01 12:48 ` Thomas Lamprecht
2020-11-01 13:14 ` Bernhard Dick
2020-11-01 19:48 ` Thomas Lamprecht
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=1bea39e7-d656-d809-0774-baa935479f53@bdick.de \
--to=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