The build-in backup works inside qemu. Each new block needs to be written twice. Once to the backup storage and once to the VM storage. This means that the slowest storage will determine the storage speed of the VM. In turn, the CPU load rises because of outstanding IO.Hey @spirit, my comment related to the "bringing his vm guests to their knees" which is the problem we are seeing with backups to nfs shares. CPU in the vms goes through the roof and they drop off the network when they are being backed up.
With all the trouble we've been seeing backing up to NFS and CIFS volumes during our proxmox evaluation I started looking at rbd exports today. Does your code only work if it's writing to another ceph volume? I'd like to export to local storage.
yes, only to remote rbd storage. (this is because we need to manage snapshot diff restore fast, and also we need to be able to restore files inside the backup rbd fast too)
to backup to a file, look at
https://github.com/Corsinvest/cv4pve-barc