From: "Konold, Martin" <martin.konold@konsec.com>
To: pve-user@lists.proxmox.com
Subject: [PVE-User] Backup to PBS fails
Date: Tue, 07 Sep 2021 14:00:16 +0200 [thread overview]
Message-ID: <0512086cc7b65670681424f95773841a@konsec.com> (raw)
Hi there,
I have a test setup investigating the migration from oVirt to Proxmox
which used to work nicely but now only creates single byte length
entries on PBS datastores.
Firstly backup to a cephfs storage works as expected:
root@hbase01 ~ # vzdump 100 --mode snapshot --node hbase01 --compress
zstd --all 0 --storage cephfs01 --mailnotification always
INFO: starting new backup job: vzdump 100 --mode snapshot
--mailnotification always --node hbase01 --storage cephfs01 --all 0
--compress zstd
INFO: Starting Backup of VM 100 (qemu)
INFO: Backup started at 2021-09-07 13:38:10
INFO: status = stopped
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: VM Name: CentOS-8-100.h.konsec.com
INFO: include disk 'scsi0' 'pool01:base-100-disk-0' 10G
INFO: creating vzdump archive
'/mnt/pve/cephfs01/dump/vzdump-qemu-100-2021_09_07-13_38_10.vma.zst'
INFO: starting template backup
INFO: /usr/bin/vma create -v -c
/mnt/pve/cephfs01/dump/vzdump-qemu-100-2021_09_07-13_38_10.tmp/qemu-server.conf
exec:zstd --rsyncable --threads=1 >
/mnt/pve/cephfs01/dump/vzdump-qemu-100-2021_09_07-13_38_10.vma.dat
drive-scsi0=/dev/rbd/pool01/base-100-disk-0
INFO: progress 0% 0/10737418240 0
INFO: progress 1% 107413504/10737418240 64716800
....
Backup to a Proxmox Backup Server PBS fails though
root@hbase01 ~ # vzdump 100 --mode snapshot --node hbase01 --compress
zstd --all 0 --storage PVE-FE-3 --mailnotification always
INFO: starting new backup job: vzdump 100 --all 0 --node hbase01
--mailnotification always --storage PVE-FE-3 --mode snapshot --compress
zstd
INFO: Starting Backup of VM 100 (qemu)
INFO: Backup started at 2021-09-07 13:38:31
INFO: status = stopped
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: VM Name: CentOS-8-100.h.konsec.com
INFO: include disk 'scsi0' 'pool01:base-100-disk-0' 10G
INFO: creating Proxmox Backup Server archive
'vm/100/2021-09-07T11:38:31Z'
INFO: starting kvm to execute backup task
Use of uninitialized value in split at
/usr/share/perl5/PVE/QemuServer/Cloudinit.pm line 100.
/dev/rbd45
generating cloud-init ISO
ERROR: VM 100 qmp command 'backup' failed - backup connect failed:
command error: EACCES: Permission denied
INFO: aborting backup job
INFO: stopping kvm after backup task
trying to acquire lock...
OK
ERROR: Backup of VM 100 failed - VM 100 qmp command 'backup' failed -
backup connect failed: command error: EACCES: Permission denied
INFO: Failed at 2021-09-07 13:38:33
INFO: Backup job finished with errors
job errors
The target storage exists and is known to PVE.
root@hbase01 ~ # pvesm status
Name Type Status Total Used
Available %
PVE-FE pbs active 59826418816 1498314752
58328104064 2.50%
PVE-FE-2 pbs active 58345629568 17525504
58328104064 0.03%
PVE-FE-3 pbs active 58345629568 17525504
58328104064 0.03%
cephfs01 cephfs active 1128591360 39051264
1089540096 3.46%
local dir active 15718400 10359288
5359112 65.91%
pool01 rbd active 1485625252 396081828
1089543424 26.66%
pool12 rbd active 4253993533 2619678397
1634315136 61.58%
Is this a problem introduced with an update of PBS?
I tried adding backup users to PBS and using API-tokens to no avail.
Both PVE and PBS are most uptodate (no-subscription)
--
Regards
ppa. Martin Konold
--
Martin Konold - Prokurist, CTO
KONSEC GmbH - make things real
Amtsgericht Stuttgart, HRB 23690
Geschäftsführer: Andreas Mack
Im Köller 3, 70794 Filderstadt, Germany
next reply other threads:[~2021-09-07 12:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-07 12:00 Konold, Martin [this message]
2021-09-07 15:22 Dietmar Maurer
2021-09-07 15:48 ` Konold, Martin
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=0512086cc7b65670681424f95773841a@konsec.com \
--to=martin.konold@konsec.com \
--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 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.