Proxmox and PBS - "starting first sync" - local vm dump dir

[voarsh]

it takes about 1 hour/1.5 hours to backup currently, and the first step is putting the entire image in the Proxmox tmpdir/vzdump dir - this is taking over 45/55 minutes, and then... after the tmpdir/vzdump dir , it should copy/"increment" the backup. However, it doesn't seem much faster than just doing a full backup if it's just making a full copy in the first round, then sending it off to PBS. (I refer to /etc/vzdump.conf)

It doesn't seem much faster to me when the first round of backing up with PBS is making a full copy to my local tmpdir/vzdump dir (which can take a while unless you're on SSD.... and then giving it to PBS...

I am running PBS as an LXC (to test this system) and made directly attached storage available for the backup. Am I missing something? Because if it's doing a full copy and putting it into tmpdir/vzdump dir and then copying it over to PBS, I'm not sure it's very fast.


Any thoughts on this?

 

[che]

it takes about 1 hour/1.5 hours to backup currently, and the first step is putting the entire image in the Proxmox tmpdir/vzdump dir - this is taking over 45/55 minutes, and then... after the tmpdir/vzdump dir , it should copy/"increment" the backup. However, it doesn't seem much faster than just doing a full backup if it's just making a full copy in the first round, then sending it off to PBS. (I refer to /etc/vzdump.conf)

It doesn't seem much faster to me when the first round of backing up with PBS is making a full copy to my local tmpdir/vzdump dir (which can take a while unless you're on SSD.... and then giving it to PBS...

I am running PBS as an LXC (to test this system) and made directly attached storage available for the backup. Am I missing something? Because if it's doing a full copy and putting it into tmpdir/vzdump dir and then copying it over to PBS, I'm not sure it's very fast.


Any thoughts on this?

Are you sure you are backing up using the proxmox-backup-client and not vzdump?
proxmox-backup-client will most certainly not place a copy of your VM data in a vzdump tmpdir...

Did you set up PBS on the PVE host as pbs storage backend as described here? https://pbs.proxmox.com/docs/pve-integration.html

 

[voarsh]

Are you sure you are backing up using the proxmox-backup-client and not vzdump?
proxmox-backup-client will most certainly not place a copy of your VM data in a vzdump tmpdir...

Did you set up PBS on the PVE host as pbs storage backend as described here? https://pbs.proxmox.com/docs/pve-integration.html

So, PBS was added under data center -> storage
A backup request was made for an LXC and because of mount points it does suspend mode, I found that all the backups were doing the usual vzdump tmpdir and then sending it to PBS.
I couldn't seem to get any VM's to backup either:

INFO: starting new backup job: vzdump 108 --mode snapshot --storage PBS --node HPProliantDL360PGen8 --remove 0 INFO: Starting Backup of VM 108 (qemu) INFO: Backup started at 2021-04-04 17:16:31 INFO: status = running INFO: VM Name: Win10Pro INFO: exclude disk 'ide0' 'FourteenTBExpansionUSB5:108/vm-108-disk-0.qcow2' (backup=no) INFO: include disk 'ide1' 'FourteenTBExpansionUSB5:108/vm-108-disk-1.qcow2' 160G INFO: backup mode: snapshot INFO: ionice priority: 7 INFO: creating Proxmox Backup Server archive 'vm/108/2021-04-04T16:16:31Z' ERROR: VM 108 qmp command 'backup' failed - backup register image failed: command error: ENODEV: No such device INFO: aborting backup job ERROR: Backup of VM 108 failed - VM 108 qmp command 'backup' failed - backup register image failed: command error: ENODEV: No such device INFO: Failed at 2021-04-04 17:16:31 INFO: Backup job finished with errors TASK ERROR: job errors

 

[che]

ERROR: VM 108 qmp command 'backup' failed - backup register image failed: command error: ENODEV: No such device

It seems that there is an issue with detecting one of your volumes. Please post the output of pveversion -v and qm config 108

 

[voarsh]

It seems that there is an issue with detecting one of your volumes. Please post the output of pveversion -v and qm config 108

Sorry for the late reply.

pveversion -v proxmox-ve: 6.3-1 (running kernel: 5.4.106-1-pve) pve-manager: 6.3-6 (running version: 6.3-6/2184247e) pve-kernel-5.4: 6.3-8 pve-kernel-helper: 6.3-8 pve-kernel-5.4.106-1-pve: 5.4.106-1 pve-kernel-5.4.101-1-pve: 5.4.101-1 pve-kernel-5.4.78-2-pve: 5.4.78-2 pve-kernel-5.4.34-1-pve: 5.4.34-2 ceph-fuse: 12.2.11+dfsg1-2.1+b1 corosync: 3.1.0-pve1 criu: 3.11-3 glusterfs-client: 5.5-3 ifupdown: residual config ifupdown2: 3.0.0-1+pve3 ksm-control-daemon: 1.3-1 libjs-extjs: 6.0.1-10 libknet1: 1.20-pve1 libproxmox-acme-perl: 1.0.8 libproxmox-backup-qemu0: 1.0.3-1 libpve-access-control: 6.1-3 libpve-apiclient-perl: 3.1-3 libpve-common-perl: 6.3-5 libpve-guest-common-perl: 3.1-5 libpve-http-server-perl: 3.1-1 libpve-storage-perl: 6.3-8 libqb0: 1.0.5-1 libspice-server1: 0.14.2-4~pve6+1 lvm2: 2.03.02-pve4 lxc-pve: 4.0.6-2 lxcfs: 4.0.6-pve1 novnc-pve: 1.1.0-1 proxmox-backup-client: 1.0.13-1 proxmox-mini-journalreader: 1.1-1 proxmox-widget-toolkit: 2.4-9 pve-cluster: 6.2-1 pve-container: 3.3-4 pve-docs: 6.3-1 pve-edk2-firmware: 2.20200531-1 pve-firewall: 4.1-3 pve-firmware: 3.2-2 pve-ha-manager: 3.1-1 pve-i18n: 2.3-1 pve-qemu-kvm: 5.2.0-5 pve-xtermjs: 4.7.0-3 qemu-server: 6.3-10 smartmontools: 7.2-pve2 spiceterm: 3.1-1 vncterm: 1.6-2 zfsutils-linux: 2.0.4-pve1

This backup issue happens to all VM's. It's only just about working for LXC's - although when suspend is used it's using vzdump tmpdir

qm config 108 bootdisk: ide0 cores: 4 description: HPBay8-108 unused%0A4TB NFS share hotplug: disk,network,usb,memory,cpu ide0: FourteenTBExpansionUSB5:108/vm-108-disk-0.qcow2,backup=0,size=17G ide1: FourteenTBExpansionUSB5:108/vm-108-disk-1.qcow2,size=160G ide2: FourteenTBExpansionUSB5:iso/Windows_10_Pro_en-US_v1909_x64_BiT_Activated.iso,media=cdrom ide3: FourteenTBExpansionUSB5:108/vm-108-disk-2.qcow2,cache=unsafe,discard=on,size=11000G memory: 2048 name: Win10Pro net0: e1000=36:F4:6A:D5:2E:FC,bridge=vmbr0,firewall=1 numa: 1 ostype: win10 parent: beforeasus scsihw: virtio-scsi-pci smbios1: uuid=2c12422b-17b6-48db-9f33-f259a5c060ac sockets: 1 vmgenid: 4059b864-944f-4b9d-a730-c75797ba1db4