Proxmox VM shuts down during backup

Emmanuel92

New Member
Jul 24, 2019
6
0
1
36
Good day all,

One of the proxmox vm's shuts down when backups are being done, probably around 15%, then gives an 'error vm not running'. it has never done it before, it's doing it all the time now, the other vm's are fine.

Are there any suggestions?

'
103elfriede-pcFAILED00:11:11VM 103 not running

103: 2019-12-09 22:37:59 INFO: Starting Backup of VM 103 (qemu)
103: 2019-12-09 22:37:59 INFO: status = running
103: 2019-12-09 22:37:59 INFO: update VM 103: -lock backup
103: 2019-12-09 22:37:59 INFO: VM Name: elfriede-pc
103: 2019-12-09 22:37:59 INFO: include disk 'ide0' 'zfs_p2:vm-103-disk-0' 250G
103: 2019-12-09 22:37:59 INFO: backup mode: snapshot
103: 2019-12-09 22:37:59 INFO: ionice priority: 7
103: 2019-12-09 22:37:59 INFO: HOOK: backup-start snapshot 103
103: 2019-12-09 22:37:59 INFO: HOOK-ENV: vmtype=qemu;dumpdir=/var/lib/vz/dump/dump;hostname=elfriede-pc;tarfile=/var/lib/vz/dump/dump/vzdump-qemu-103-2019_12_09-22_37_59.vma.lzo;logfile=/var/lib/vz/dump/dump/vzdump-qemu-103-2019_12_09-22_37_59.log
103: 2019-12-09 22:37:59 INFO: HOOK: pre-stop snapshot 103
103: 2019-12-09 22:37:59 INFO: HOOK: pre-restart snapshot 103
103: 2019-12-09 22:37:59 INFO: HOOK: post-restart snapshot 103
103: 2019-12-09 22:37:59 INFO: creating archive '/var/lib/vz/dump/dump/vzdump-qemu-103-2019_12_09-22_37_59.vma.lzo'
103: 2019-12-09 22:37:59 INFO: started backup task 'c9619244-1bca-4c3b-b906-bca78d9155c5'
103: 2019-12-09 22:38:02 INFO: status: 0% (36962304/268435456000), sparse 0% (122880), duration 3, read/write 12/12 MB/s
103: 2019-12-09 22:39:00 INFO: status: 1% (2706374656/268435456000), sparse 0% (17272832), duration 61, read/write 46/45 MB/s
103: 2019-12-09 22:40:06 INFO: status: 2% (5431754752/268435456000), sparse 0% (43081728), duration 127, read/write 41/40 MB/s
103: 2019-12-09 22:40:38 INFO: status: 3% (8145731584/268435456000), sparse 0% (157728768), duration 159, read/write 84/81 MB/s
103: 2019-12-09 22:41:16 INFO: status: 4% (10779885568/268435456000), sparse 0% (283955200), duration 197, read/write 69/65 MB/s
103: 2019-12-09 22:41:59 INFO: status: 5% (13467254784/268435456000), sparse 0% (445317120), duration 240, read/write 62/58 MB/s
103: 2019-12-09 22:42:37 INFO: status: 6% (16127819776/268435456000), sparse 0% (549953536), duration 278, read/write 70/67 MB/s
103: 2019-12-09 22:43:21 INFO: status: 7% (18845663232/268435456000), sparse 0% (668078080), duration 322, read/write 61/59 MB/s
103: 2019-12-09 22:43:51 INFO: status: 8% (21483552768/268435456000), sparse 0% (799899648), duration 352, read/write 87/83 MB/s
103: 2019-12-09 22:44:31 INFO: status: 9% (24265555968/268435456000), sparse 0% (927531008), duration 392, read/write 69/66 MB/s
103: 2019-12-09 22:45:05 INFO: status: 10% (26865500160/268435456000), sparse 0% (953221120), duration 426, read/write 76/75 MB/s
103: 2019-12-09 22:45:40 INFO: status: 11% (29574955008/268435456000), sparse 0% (966037504), duration 461, read/write 77/77 MB/s
103: 2019-12-09 22:46:14 INFO: status: 12% (32254984192/268435456000), sparse 0% (975441920), duration 495, read/write 78/78 MB/s
103: 2019-12-09 22:47:06 INFO: status: 13% (34987638784/268435456000), sparse 0% (982171648), duration 547, read/write 52/52 MB/s
103: 2019-12-09 22:47:59 INFO: status: 14% (37632737280/268435456000), sparse 0% (982589440), duration 600, read/write 49/49 MB/s
103: 2019-12-09 22:48:20 INFO: status: 15% (40304181248/268435456000), sparse 0% (982949888), duration 621, read/write 127/127 MB/s
103: 2019-12-09 22:49:05 ERROR: VM 103 not running
103: 2019-12-09 22:49:05 INFO: aborting backup job
103: 2019-12-09 22:49:05 ERROR: VM 103 not running
103: 2019-12-09 22:49:10 ERROR: Backup of VM 103 failed - VM 103 not running
103: 2019-12-09 22:49:10 INFO: HOOK: backup-abort snapshot 103
103: 2019-12-09 22:49:10 INFO: HOOK-ENV: vmtype=qemu;dumpdir=/var/lib/vz/dump/dump;hostname=elfriede-pc;tarfile=/var/lib/vz/dump/dump/vzdump-qemu-103-2019_12_09-22_37_59.vma.lzo;logfile=/var/lib/vz/dump/dump/vzdump-qemu-103-2019_12_09-22_37_59.log



Thank you

Regards
Emmanuel
 
Is it possible that there is something inside the VM triggering the shutdown? What do the logs in the VM say? If it's a Linux Guest you might have to enable persistent systemd journals.
 

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!