Search results

Hi, as we're often migrate VMs between nodes and even clusters we have sometimes orphaned VM backups on our PBS hosts. Did I miss something, or isnt it possible to prune by date? Example: We do weekly backups of VM an the VM gets migrated to another PVE cluster, so the backup of it is then on...

Here you go: https://github.com/robhost/proxmox-scripts/blob/master/vzdump_hook.sh :)

Okay, got something "strange" on the host: Mar 19 01:50:06 hav203 qmeventd[1346]: error parsing vmid for 31032: Success We've got a hook script running which increases the VM IOPS during backups - maybe this causes the problem here?

There is nothing in there at this time, not even an entry ;) Can we expand logging or enable debug?

There is nothing in the logs on the PVE host, no OOM and nothing else. The ist the task log: INFO: Starting Backup of VM 5242 (qemu) INFO: Backup started at 2021-03-19 01:50:04 INFO: status = running INFO: VM Name: vs5242 INFO: include disk 'scsi0' 'ceph-vs:vm-5242-disk-0' 250G INFO: backup...

The problem persists, making PBS not usable so far :( How to get further infos, why don't you print the signal number within the error?

Nope, only the vzdump output from the last posting.

Just happened again and killed the whole backup job, see attached image. Before it made 10 VM backups without problems./ INFO: update VM 5065: -scsi0 nvme0:5065/vm-5065-disk-0.qcow2,cache=writeback,discard=on,format=qcow2,size=250G,iops_rd=1000,iops_rd_max=15000,iops_wr=500,iops_wr_max=7500...

No - we will do another backup full-run and report back if the error comes up again.

Hi, our PBS backups from PVE (both latest versions) are failing sometimes with "interrupted by signal" - but there is no further info in the logs, only this: INFO: creating Proxmox Backup Server archive 'vm/5297/2021-02-25T22:30:00Z' ERROR: Backup of VM 5297 failed - interrupted by signal...

You can mount the VM backup and restore files from there, no problem.

I'm also looking into this, but with the proxmox-backup-client on Linux: 1st backup of a folder: www.pxar: had to upload 28.88 GiB of 29.61 GiB in 2704.82s, average speed 10.93 MiB/s). www.pxar: backup was done incrementally, reused 753.43 MiB (2.5%) 2nd backup directly after that: www.pxar...

Works, very nice! Thanks! I think Proxmox should adopt this, as the lack of an official RHEL backup client and the main focus on Debian is really a drawback of PBS at the moment. What do you think @tom ?

Thanks, will test it soon :)

Nice, thanks. What about a RHEL8 build? :)

We updated the Ceph client packages on the PVE nodes to 15.2.8-pve2 and restore works now as expected. The rbd itself has the same features still, so this must somehow depend on librbd. Thanks for that hint and your help, we will now do further tests with PBS :)

The packages on the Ceph nodes are the official ones from here: http://download.ceph.com/debian-octopus/dists/bionic/ Ceph on the PVE nodes comes from the Debian dist and is quite old: 12.2.11+dfsg1-2.1+b1 We'll try the upgrade to the Octopus packages on the PVE nodes as next step and report...

Sorry, here comes the rest: agent: 1 boot: order=scsi0 cores: 2 cpu: Haswell-noTSX-IBRS,flags=+pcid;+spec-ctrl;+ssbd memory: 2048 migrate_speed: 512 name: vs5480 net0: virtio=52:54:6F:99:A5:90,bridge=vmbr504,firewall=1 onboot: 1 ostype: l26 protection: 1 scsi0...

Thats right. The problem only happens with PBS. Ceph runs on Ubuntu 18.04 LTS from the official Ceph repo .

Can you test with EL 8? Maybe kernel related or depending on the qemu-guest-agent version, as we're 100% on EL ;) Versions: pve-manager/6.3-3/eee5f901 (running kernel: 5.4.78-2-pve) proxmox-backup-server 1.0.8-1 running version: 1.0.8 And no, we have no Ceph, PVE oder PBS errors. With...