Hello. There are difficulties in creating a backup of a virtual machine running Windows Server 2019 with the Exchange role, while using the PVE manager version pve-manager/7.4-17/513c62be. The Windows services and the qemu-agent become unresponsive. After canceling the backup creation, the services start working again and everything functions properly. I will provide the VM logs and configurations.
PBS version 2.4.1
This command 'fs-thaw' starting crashing qemu-agent
journal logs
PBS version 2.4.1
This command 'fs-thaw' starting crashing qemu-agent
Code:
INFO: starting new backup job: vzdump 196 --node host112 --storage pbs01 --notes-template '{{guestname}}' --remove 0 --mode snapshot
INFO: Starting Backup of VM 196 (qemu)
INFO: Backup started at 2023-12-04 13:48:23
INFO: status = running
INFO: VM Name: exchange-01
INFO: include disk 'ide0' 'PVE7:vm-196-disk-1' 70G
INFO: include disk 'ide1' 'PVE7:vm-196-disk-2' 3000G
INFO: include disk 'ide3' 'PVE2:vm-196-disk-0' 120G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: skip unused drive 'PVE7:vm-196-disk-0' (not included into backup)
INFO: skip unused drive 'PVE7:vm-196-disk-3' (not included into backup)
INFO: pending configuration changes found (not included into backup)
INFO: creating Proxmox Backup Server archive 'vm/196/2023-12-04T02:48:23Z'
INFO: issuing guest-agent 'fs-freeze' command
INFO: issuing guest-agent 'fs-thaw' command
ERROR: VM 196 qmp command 'guest-fsfreeze-thaw' failed - got timeout
INFO: started backup task '2b869ec9-d82b-4032-8d8f-62e6c80020f9'
INFO: resuming VM again
INFO: ide0: dirty-bitmap status: existing bitmap was invalid and has been cleared
INFO: ide1: dirty-bitmap status: existing bitmap was invalid and has been cleared
INFO: ide3: dirty-bitmap status: existing bitmap was invalid and has been cleared
INFO: 0% (22.6 GiB of 3.1 TiB) in 3s, read: 7.5 GiB/s, write: 7.5 GiB/s
INFO: 1% (32.0 GiB of 3.1 TiB) in 1m 11s, read: 141.4 MiB/s, write: 141.4 MiB/s
INFO: 2% (64.4 GiB of 3.1 TiB) in 4m 10s, read: 185.3 MiB/s, write: 134.9 MiB/s
ERROR: interrupted by signal
INFO: aborting backup job
INFO: resuming VM again
ERROR: Backup of VM 196 failed - interrupted by signal
INFO: Failed at 2023-12-04 13:57:18
ERROR: Backup job failed - interrupted by signal
TASK ERROR: interrupted by signal
Code:
Dec 04 13:48:22 host112 pvedaemon[2374110]: <username> starting task UPID:host17:0024A995:051D3582:656D3DF6:vzdump:196:username:
Dec 04 13:48:23 host112 pvedaemon[2402709]: INFO: starting new backup job: vzdump 196 --node host112 --storage pbs01 --notes-template '{{guestname}}' --remove 0 --mode snapshot
Dec 04 13:48:23 host112 pvedaemon[2402709]: INFO: Starting Backup of VM 196 (qemu)
Dec 04 13:50:27 host112 pvedaemon[2306795]: worker exit
Dec 04 13:50:27 host112 pvedaemon[1619]: worker 2306795 finished
Dec 04 13:50:27 host112 pvedaemon[1619]: starting 1 worker(s)
Dec 04 13:50:27 host112 pvedaemon[1619]: worker 2405574 started
Dec 04 13:50:43 host112 pvedaemon[2391818]: VM 196 qmp command failed - VM 196 qmp command 'guest-ping' failed - got timeout
Dec 04 13:51:03 host112 pvedaemon[2374110]: VM 196 qmp command failed - VM 196 qmp command 'guest-ping' failed - got timeout
Dec 04 13:51:23 host112 pvedaemon[2405574]: VM 196 qmp command failed - VM 196 qmp command 'guest-ping' failed - unable to connect to VM 196 qga socket - timeout after 31 retries
Dec 04 13:51:28 host112 pvedaemon[2402709]: VM 196 qmp command failed - VM 196 qmp command 'guest-fsfreeze-thaw' failed - got timeout
Dec 04 13:51:43 host112 pvedaemon[2405574]: VM 196 qmp command failed - VM 196 qmp command 'guest-ping' failed - got timeout
Dec 04 13:52:04 host112 pvedaemon[2391818]: VM 196 qmp command failed - VM 196 qmp command 'guest-ping' failed - got timeout
Dec 04 13:52:24 host112 pvedaemon[2374110]: VM 196 qmp command failed - VM 196 qmp command 'guest-ping' failed - got timeout
Dec 04 13:52:44 host112 pvedaemon[2405574]: VM 196 qmp command failed - VM 196 qmp command 'guest-ping' failed - got timeout
Dec 04 13:53:05 host112 pvedaemon[2391818]: VM 196 qmp command failed - VM 196 qmp command 'guest-ping' failed - got timeout
Dec 04 13:53:25 host112 pvedaemon[2374110]: VM 196 qmp command failed - VM 196 qmp command 'guest-ping' failed - got timeout
Dec 04 13:53:46 host112 pvedaemon[2405574]: VM 196 qmp command failed - VM 196 qmp command 'guest-ping' failed - got timeout
Dec 04 13:54:06 host112 pvedaemon[2374110]: VM 196 qmp command failed - VM 196 qmp command 'guest-ping' failed - got timeout
Dec 04 13:54:26 host112 pvedaemon[2391818]: VM 196 qmp command failed - VM 196 qmp command 'guest-ping' failed - got timeout
Last edited: