Can't start backup process on PBS

[Rikkert]

Hi,

Im trying to configure PBS for my PVE. I added the Datastore and connected it to PVE.
But here comes the problem everytime i want to start the backup proces i get this error:

NFO: starting new backup job: vzdump 101 --mode snapshot --storage PBS --node pve --remove 0 --notes-template '{{guestname}}'
INFO: Starting Backup of VM 101 (qemu)
INFO: Backup started at 2024-09-18 21:11:05
INFO: status = running
INFO: VM Name: EZdomain
INFO: include disk 'scsi0' 'EZdomainStorage:vm-101-disk-0' 463G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: snapshots found (not included into backup)
INFO: creating Proxmox Backup Server archive 'vm/101/2024-09-18T19:11:05Z'
ERROR: VM 101 qmp command 'backup' failed - backup register image failed: command error: EINVAL: Invalid argument
INFO: aborting backup job
INFO: resuming VM again
ERROR: Backup of VM 101 failed - VM 101 qmp command 'backup' failed - backup register image failed: command error: EINVAL: Invalid argument
INFO: Failed at 2024-09-18 21:11:05
INFO: Backup job finished with errors
TASK ERROR: job errors

Anyone who knows why?

Im running Proxmox Backup Server on a Raspberry Pi 5 with Docker.

Thanks.

 

[Chris]

Im running Proxmox Backup Server on a Raspberry Pi 5 with Docker.

Just to note this straight away, that is not an officially supported setup, as there is at the time of writing no official ARM support.

ERROR: VM 101 qmp command 'backup' failed - backup register image failed: command error: EINVAL: Invalid argument
INFO: aborting backup job
INFO: resuming VM again
ERROR: Backup of VM 101 failed - VM 101 qmp command 'backup' failed - backup register image failed: command error: EINVAL: Invalid argument

What versions of PVE and PBS are involved here? Please post the output of pveversion -v and proxmox-backup-manager version --verbose. Best in code tags for better readability.

 

[Rikkert]

Thank you for your reply,

Just to note this straight away, that is not an officially supported setup, as there is at the time of writing no official ARM support.

I know the setup is not supported, but i know it worked for other people.

What versions of PVE and PBS are involved here? Please post the output of pveversion -v and proxmox-backup-manager version --verbose. Best in code tags for better readability.

Output for pveversion -v:

proxmox-ve: 7.4-1 (running kernel: 5.15.102-1-pve)
pve-manager: 7.4-18 (running version: 7.4-18/b1f94095)
pve-kernel-5.15: 7.4-15
pve-kernel-5.15.158-2-pve: 5.15.158-2
pve-kernel-5.15.143-1-pve: 5.15.143-1
pve-kernel-5.15.102-1-pve: 5.15.102-1
ceph-fuse: 15.2.17-pve1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx4
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.4
libproxmox-backup-qemu0: 1.3.1-1
libproxmox-rs-perl: 0.2.1
libpve-access-control: 7.4.3
libpve-apiclient-perl: 3.2-2
libpve-common-perl: 7.4-2
libpve-guest-common-perl: 4.2-4
libpve-http-server-perl: 4.2-3
libpve-rs-perl: 0.7.7
libpve-storage-perl: 7.4-3
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.2-2
lxcfs: 5.0.3-pve1
novnc-pve: 1.4.0-1
proxmox-backup-client: 2.4.7-1
proxmox-backup-file-restore: 2.4.7-1
proxmox-kernel-helper: 7.4-1
proxmox-mail-forward: 0.1.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.7.4
pve-cluster: 7.3-3
pve-container: 4.4-7
pve-docs: 7.4-2
pve-edk2-firmware: 3.20230228-4~bpo11+3
pve-firewall: 4.3-5
pve-firmware: 3.6-6
pve-ha-manager: 3.6.1
pve-i18n: 2.12-1
pve-qemu-kvm: 7.2.10-1
pve-xtermjs: 4.16.0-2
qemu-server: 7.4-6
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+3
vncterm: 1.7-1
zfsutils-linux: 2.1.15-pve1

Output for proxmox-backup-manager version --verbose:

proxmox-backup                unknown              running kernel: 6.6.47+rpt-rp
proxmox-backup-server         3.2.7-1              running version: 3.2.7       
ifupdown2                     3.0.0-1.1                                         
libjs-extjs                   7.0.0-4                                           
proxmox-backup-docs           3.2.7-1                                           
proxmox-backup-client         unknown                                           
proxmox-mail-forward          unknown                                           
proxmox-mini-journalreader    1.4.0                                             
proxmox-offline-mirror-helper unknown                                           
proxmox-widget-toolkit        4.2.3                                             
pve-xtermjs                   5.3.0-3                                           
smartmontools                 7.3-1+b1                                         
zfsutils-linux                2.2.3-1~bpo12+1~rpt1

 

[Chris]

What filesystem is used for the storage backing the datastore? Might be that it does not support all the required features, see e.g. https://forum.proxmox.com/threads/virtualized-pbs-with-shared-mount.100455/

 

[Rikkert]

What filesystem is used for the storage backing the datastore? Might be that it does not support all the required features, see e.g. https://forum.proxmox.com/threads/virtualized-pbs-with-shared-mount.100455/

I made an ZFS mirror with proxmox.

Filesystem Type 1K-blocks Used Available Use% Mounted on
PBS zfs 1885863424 24960 1885838464 1% /mnt/datastore1

 

[Chris]

I made an ZFS mirror with proxmox.

Filesystem Type 1K-blocks Used Available Use% Mounted on
PBS zfs 1885863424 24960 1885838464 1% /mnt/datastore1

Is this inside the docker? Does your kernel have ZFS support? Please explain a bit more, as I am not at all familiar with your setup.

 

[Rikkert]

Is this inside the docker? Does your kernel have ZFS support? Please explain a bit more, as I am not at all familiar with your setup.

On the Raspberry Pi 5 is PiOS installed, I installed PBS via a docker and both docker, PiOS and the Pi itself support ZFS. The ZFS pool is working correctly.

But when i start the backup process it gives me the error above.

If you want specifiek logsor data please tell me.

I placed a screenshot withthe kernel version etc.

Task Viewer: Datastore BackupsEZ vm/101

2024-09-19T11:05:37+01:00: starting new backup on datastore 'BackupsEZ' from ::ffff:192.168.2.1: "vm/101/2024-09-19T10:05:36Z"
2024-09-19T11:05:37+01:00: GET /previous: 400 Bad Request: no valid previous backup
2024-09-19T11:05:37+01:00: POST /fixed_index: 400 Bad Request: EINVAL: Invalid argument
2024-09-19T11:05:37+01:00: backup ended and finish failed: backup ended but finished flag is not set.
2024-09-19T11:05:37+01:00: removing unfinished backup
2024-09-19T11:05:37+01:00: TASK ERROR: backup ended but finished flag is not set.

 

[Chris]

On the Raspberry Pi 5 is PiOS installed, I installed PBS via a docker and both docker, PiOS and the Pi itself support ZFS. The ZFS pool is working correctly.

But how are you sharing the ZFS dataset with the PBS inside the container? I suspect that layer is the root of your problem. Can you share some configs?