QEMU KVM on Rocky Linux 8.9 + Proxmox-backup-agent CLI

[calazans_br]

QEMU-KVM Environment

Rocky Linux release 8.10 (Green Obsidian)
[root@srv-kvm-01 ~]# virsh list
Id Name State
--------------------------------
1 SBC-392-450 running
[root@srv-kvm-01 ~]# virsh domblklist SBC-392-450
Target Source
-------------------------------------------------------
vda /kvmdados/vms/bordernet-3.9.2-515-disk1.qcow2
vdb /kvmdados/vms/bordernet-3.9.2-515-disk2.qcow2

Backup Environment - PROXMOX BACKUP SERVER 3.2.2
root@srv-bkp-proxmox:~# hostnamectl
Static hostname: srv-bkp-proxmox
Icon name: computer-vm
Chassis: vm
Machine ID: ca92e154bd174949b65ca4ec4f3bd098
Boot ID: 0e90292cbb5a477c89214cdc2631b2c5
Virtualization: kvm
Operating System: Debian GNU/Linux 12 (bookworm)
Kernel: Linux 6.8.4-2-pve
Architecture: x86-64
Hardware Vendor: QEMU
Hardware Model: Standard PC _i440FX + PIIX, 1996_
Firmware Version: rel-1.16.2-0-gea1b7a073390-prebuilt.qemu.org

On Rocky Linux, I installed proxmox-backup-client-3.1.2-1.el8.x86_64 and listed the backup pool as shown below:
[root@srv-kvm-01 ~]# proxmox-backup-client list --repository root@pam@192.168.XXX.XXXUMPTECH
┌────────┬─────────────────────────────┬──────────────┬─────────────────────────────────────────────────────────────────────────────────────────────────────┐
│ group │ last snapshot │ backup-count │ files │
╞════════╪═════════════════════════════╪══════════════╪═════════════════════════════════════════════════════════════════════════════════════════════════════╡
│ vm/100 │ vm/100/2024-05-31T00:00:11Z │ 5 │ client.log drive-ide0.img drive-ide1.img qemu-server.conf │
├────────┼─────────────────────────────┼──────────────┼─────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ vm/101 │ vm/101/2024-07-13T23:30:08Z │ 4 │ client.log drive-efidisk0.img drive-ide0.img drive-tpmstate0-backup.img index.json qemu-server.conf │
├────────┼─────────────────────────────┼──────────────┼─────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ vm/102 │ vm/102/2024-07-11T23:32:15Z │ 4 │ client.log drive-efidisk0.img drive-ide0.img drive-tpmstate0-backup.img qemu-server.conf │
├────────┼─────────────────────────────┼──────────────┼─────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ vm/103 │ vm/103/2024-06-04T23:33:35Z │ 7 │ client.log drive-scsi0.img index.json qemu-server.conf │
├────────┼─────────────────────────────┼──────────────┼─────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ vm/104 │ vm/104/2024-05-30T17:29:36Z │ 1 │ client.log drive-sata0.img drive-scsi0.img index.json qemu-server.conf │
├────────┼─────────────────────────────┼──────────────┼─────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ vm/200 │ vm/200/2024-07-14T06:00:09Z │ 5 │ client.log drive-ide0.img index.json qemu-server.conf │
├────────┼─────────────────────────────┼──────────────┼─────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ vm/401 │ vm/401/2024-07-14T07:00:00Z │ 5 │ client.log drive-ide0.img drive-ide1.img index.json qemu-server.conf │
├────────┼─────────────────────────────┼──────────────┼─────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ vm/450 │ vm/450/2024-07-14T06:01:40Z │ 5 │ client.log drive-sata0.img index.json qemu-server.conf │
├────────┼─────────────────────────────┼──────────────┼─────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ vm/500 │ vm/500/2024-07-13T23:33:55Z │ 4 │ client.log drive-sata0.img index.json qemu-server.conf │
├────────┼─────────────────────────────┼──────────────┼─────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ vm/600 │ vm/600/2024-07-13T23:34:23Z │ 4 │ client.log drive-sata0.img drive-sata1.img index.json qemu-server.conf │
├────────┼─────────────────────────────┼──────────────┼─────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ vm/661 │ vm/661/2024-07-14T06:03:18Z │ 5 │ client.log drive-efidisk0.img drive-scsi0.img drive-scsi1.img index.json qemu-server.conf │
└────────┴─────────────────────────────┴──────────────┴─────────────────────────────────────────────────────────────────────────────────────────────────────┘

How can I perform a backup of the VM SBC-392-450?

I tried the commands below which resulted in syntax errors.

#proxmox-backup-client backup --backup-type vm SBC-392-450 --repository root@pam@192.168.39.64UMPTECH
#proxmox-backup-client backup --repository root@pbs@192.168.XXX.XXXUMPTECH --backup-id SBC-392-450 /kvmdados/vms/bordernet-3.9.2-515-disk1.qcow2 /kvmdados/vms/bordernet-3.9.2-515-disk2.qcow2
#proxmox-backup-client backup --repository root@pam@192.168.XXX.XXXUMPTECH --backup-type vm --backup-id SBC-392-450 /kvmdados/vms/bordernet-3.9.2-515-disk1.qcow2 /kvmdados/vms/bordernet-3.9.2-515-disk2.qcow2

Based on what has been reported, I am seeking assistance from contributors.

• CLI Documentation - Did not help
• Internet Search - Did not help
• ChatGPT - Did not help

Thank you very much.

 

[dcsapak]

as the docs describe: https://pbs.proxmox.com/docs/backup-client.html#creating-backups

you have to give a 'backupspec' either a '.pxar' or a '.img' file
in both cases you have to make sure the source is consistent (e.g. an img file of a running vm will probably be corrupted if backed up in this way)

e.g. a working cli could be

proxmox-backup-client --repository <...> foo.pxar:/dir/to/backup
proxmox-backup-client --repository <...> foo.img:/img/file/to/backup.img

backing up running vms though is currently only working on a proxmox ve host, since there we make use of our custom qemu and start the backup from there