[SOLVED] Backup job cannot be completed

BrotherJ

Active Member
Sep 14, 2019
31
2
28
32
Hi,
my running Proxmox-Server is:
Code:
pveversion -v
proxmox-ve: 8.0.2 (running kernel: 6.2.16-15-pve)
pve-manager: 8.0.4 (running version: 8.0.4/d258a813cfa6b390)
pve-kernel-6.2: 8.0.5
proxmox-kernel-helper: 8.0.3
proxmox-kernel-6.2.16-15-pve: 6.2.16-15
proxmox-kernel-6.2: 6.2.16-15
pve-kernel-6.2.16-3-pve: 6.2.16-3
ceph-fuse: 17.2.6-pve1+3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx5
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-4
libknet1: 1.26-pve1
libproxmox-acme-perl: 1.4.6
libproxmox-backup-qemu0: 1.4.0
libproxmox-rs-perl: 0.3.1
libpve-access-control: 8.0.5
libpve-apiclient-perl: 3.3.1
libpve-common-perl: 8.0.9
libpve-guest-common-perl: 5.0.5
libpve-http-server-perl: 5.0.4
libpve-rs-perl: 0.8.5
libpve-storage-perl: 8.0.2
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 5.0.2-4
lxcfs: 5.0.3-pve3
novnc-pve: 1.4.0-2
proxmox-backup-client: 3.0.3-1
proxmox-backup-file-restore: 3.0.3-1
proxmox-kernel-helper: 8.0.3
proxmox-mail-forward: 0.2.0
proxmox-mini-journalreader: 1.4.0
proxmox-widget-toolkit: 4.0.9
pve-cluster: 8.0.4
pve-container: 5.0.4
pve-docs: 8.0.5
pve-edk2-firmware: 3.20230228-4
pve-firewall: 5.0.3
pve-firmware: 3.8-2
pve-ha-manager: 4.0.2
pve-i18n: 3.0.7
pve-qemu-kvm: 8.0.2-6
pve-xtermjs: 4.16.0-3
qemu-server: 8.0.7
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.1.13-pve1
Since January 25th This year there is a backup job of the VM running with VMID 103, which is displayed in the dashboard under Tasks.
I now want to change something in the HW configuration of this VM. This doesn't work because then the message "VM is locked (backup) (500)" comes up.
On the other hand, I can't find a way to stop this backup job or kill it using the "kill" command like in Linux Bash.

Do you have a solution on how to stop the backup job?

Best regards
BrotherJ
 
Hi,

May you please post the processID information about the backup? You can get the information about the process of the backup using like the following command:

Bash:
ps aux | egrep "vzdump|103"

And please also the VM config `qm config 103`
 
Hello Moayad,

here are the process informations

Code:
root@neckar1 ~ # ps aux | egrep "vzdump|103"
root        1032  0.0  0.0      0     0 ?        I<    2023   3:05 [kworker/17:1H-kblockd]
root        1037  0.0  0.0      0     0 ?        I<    2023   3:11 [kworker/61:1H-kblockd]
root        2103  0.0  0.0      0     0 ?        S<    2023 120:01 [z_wr_int_5]
root       10359  0.0  0.0      0     0 ?        S     2023  11:53 [vhost-9202]
root      473744  6.2  4.8 10174736 6416128 ?    Sl   Jan08 3144:51 /usr/bin/kvm -id 103 -name Apache-Server-Web,debug-threads=on -no-shutdown -chardev socket,id=qmp,path=/var/run/qemu-server/
103.qmp,server=on,wait=off -mon chardev=qmp,mode=control -chardev socket,id=qmp-event,path=/var/run/qmeventd.sock,reconnect=5 -mon chardev=qmp-event,mode=control -pidfile /var/run/qemu-server/
103.pid -daemonize -smbios type=1,uuid=4bd30ecb-9ca3-41b6-ad6a-6439383fc78d -smp 12,sockets=3,cores=4,maxcpus=12 -nodefaults -boot menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-
server/bootsplash.jpg -vnc unix:/var/run/qemu-server/103.vnc,password=on -cpu kvm64,enforce,+kvm_pv_eoi,+kvm_pv_unhalt,+lahf_lm,+sep -m 6144 -device pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,
addr=0x1e -device pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f -device piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2 -device usb-tablet,id=tablet,bus=uhci.0,port=1 -device VGA,id=vga,b
us=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3,free-page-reporting=on -iscsi initiator-name=iqn.1993-08.org.debian:01:4ec242395dd0 -drive file=/var/lib/pve/local-b
trfs/template/iso/debian-10.6.0-amd64-netinst.iso,if=none,id=drive-ide2,media=cdrom,aio=io_uring -device ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200 -device virtio-scsi-pci,
id=scsihw0,bus=pci.0,addr=0x5 -drive file=/dev/zvol/zp_100/vm-103-disk-1,if=none,id=drive-scsi0,cache=writethrough,format=raw,aio=io_uring,detect-zeroes=on -device scsi-hd,bus=scsihw0.0,channe
l=0,scsi-id=0,lun=0,drive=drive-scsi0,id=scsi0 -drive file=/dev/zvol/zp_100/vm-103-disk-2,if=none,id=drive-scsi1,cache=writethrough,format=raw,aio=io_uring,detect-zeroes=on -device scsi-hd,bus
=scsihw0.0,channel=0,scsi-id=0,lun=1,drive=drive-scsi1,id=scsi1 -drive file=/dev/disk/by-id/dm-uuid-LVM-jxzylD83jEI75Lii7T8a9DtPshp4W7i3N5i7UupiyFDYufgcOnAALGzrG1QG01QZ,if=none,id=drive-scsi2,
format=raw,cache=none,aio=io_uring,detect-zeroes=on -device scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=2,drive=drive-scsi2,id=scsi2 -device ahci,id=ahci0,multifunction=on,bus=pci.0,addr=0x7
-drive file=/dev/zvol/zp_100/vm-103-disk-0,if=none,id=drive-sata0,cache=writethrough,format=raw,aio=io_uring,detect-zeroes=on -device ide-hd,bus=ahci0.0,drive=drive-sata0,id=sata0,bootindex=1
03 -netdev type=tap,id=net0,ifname=tap103i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on -device virtio-net-pci,mac=12:27:A3:31:1E:6F,netdev=n
et0,bus=pci.0,addr=0x12,id=net0,rx_queue_size=1024,tx_queue_size=256,bootindex=300 -netdev type=tap,id=net1,ifname=tap103i1,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-serv
er/pve-bridgedown,vhost=on -device virtio-net-pci,mac=1A:4E:A3:95:59:7E,netdev=net1,bus=pci.0,addr=0x13,id=net1,rx_queue_size=1024,tx_queue_size=256,bootindex=301 -machine type=pc+pve0
root     1410328  0.0  0.0      0     0 ?        S     2023   0:00 [vhost-1408233]
root     2277343  0.0  0.0   6332  1536 pts/0    S+   11:36   0:00 grep -E vzdump|103
root     3098899  0.1  0.0 223816 110932 ?       Ss   Jan25  31:03 task UPID:neckar1:002F4913:2F931AD9:65B19670:vzdump::root@pam:

and the configuration of the VM:
Code:
root@neckar1 ~ # qm config 103
bootdisk: sata0
cores: 4
ide2: local-btrfs:iso/debian-10.6.0-amd64-netinst.iso,media=cdrom
lock: backup
memory: 6144
name: Apache-Server-Web
net0: virtio=12:27:A3:31:1E:6F,bridge=vmbr0
net1: virtio=1A:4E:A3:95:59:7E,bridge=vmbr1
numa: 0
onboot: 1
ostype: l26
sata0: zp_100:vm-103-disk-0,cache=writethrough,size=150G
scsi0: zp_100:vm-103-disk-1,cache=writethrough,size=500G
scsi1: zp_100:vm-103-disk-2,cache=writethrough,size=300G
scsi2: /dev/disk/by-id/dm-uuid-LVM-jxzylD83jEI75Lii7T8a9DtPshp4W7i3N5i7UupiyFDYufgcOnAALGzrG1QG01QZ,size=1G
scsihw: virtio-scsi-pci
smbios1: uuid=4bd30ecb-9ca3-41b6-ad6a-6439383fc78d
sockets: 3
unused0: local-btrfs:103/vm-103-disk-0.raw

Best regards

BrotherJ
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!