[SOLVED] VM suddenly Shuts off when takeing backup

thomasloldk

New Member
Nov 30, 2015
7
0
1
Denmark
Hey Thare.

I have a standalone Proxmox VE 4.2 running in a production environment.
I take snapshot backup of all my vm's from Tuesday - saturday night.

My problem is that i have migrated an old physel windows 2003 ISS server to a VM on my server,
But somtimes when we take backup of it, it suddenly shuts off at 22-28 %.
I have tried looking in the logs but i can't find the problem anywhare.
Do you have any tips on how i furthuer investigate this ?

None of my other 3 linux servers does this...


OUTPUT og last fail:
105: Aug 31 00:48:29 INFO: Starting Backup of VM 105 (qemu)
105: Aug 31 00:48:29 INFO: status = running
105: Aug 31 00:48:29 INFO: update VM 105: -lock backup
105: Aug 31 00:48:30 INFO: backup mode: snapshot
105: Aug 31 00:48:30 INFO: ionice priority: 7
105: Aug 31 00:48:30 INFO: creating archive '/mnt/pve/IMTNodeBackup/dump/vzdump-qemu-105-2016_08_31-00_48_29.vma.lzo'
105: Aug 31 00:48:30 INFO: started backup task '3532cdcf-713e-473f-9ec3-4c528987e05b'
105: Aug 31 00:48:33 INFO: status: 0% (186253312/240057409536), sparse 0% (3227648), duration 3, 62/61 MB/s
105: Aug 31 00:49:20 INFO: status: 1% (2401763328/240057409536), sparse 0% (39690240), duration 50, 47/46 MB/s
105: Aug 31 00:49:38 INFO: status: 2% (5234098176/240057409536), sparse 0% (1880883200), duration 68, 157/55 MB/s
105: Aug 31 00:49:44 INFO: status: 3% (8019574784/240057409536), sparse 1% (4666294272), duration 74, 464/0 MB/s
105: Aug 31 00:49:47 INFO: status: 13% (33274068992/240057409536), sparse 12% (29875900416), duration 77, 8418/14 MB/s
105: Aug 31 00:49:54 INFO: status: 14% (33652670464/240057409536), sparse 12% (29880397824), duration 84, 54/53 MB/s
105: Aug 31 00:50:07 INFO: status: 15% (36062625792/240057409536), sparse 13% (31620214784), duration 97, 185/51 MB/s
105: Aug 31 00:51:04 INFO: status: 16% (38446694400/240057409536), sparse 13% (31708655616), duration 154, 41/40 MB/s
105: Aug 31 00:51:49 INFO: status: 17% (40819884032/240057409536), sparse 13% (31845339136), duration 199, 52/49 MB/s
105: Aug 31 00:52:43 INFO: status: 18% (43210506240/240057409536), sparse 13% (32060686336), duration 253, 44/40 MB/s
105: Aug 31 00:53:33 INFO: status: 19% (45641826304/240057409536), sparse 13% (32413741056), duration 303, 48/41 MB/s
105: Aug 31 00:54:29 INFO: status: 20% (48059908096/240057409536), sparse 13% (32792444928), duration 359, 43/36 MB/s
105: Aug 31 00:55:22 INFO: status: 21% (50457739264/240057409536), sparse 13% (33075961856), duration 412, 45/39 MB/s
105: Aug 31 00:56:19 INFO: status: 22% (52823719936/240057409536), sparse 13% (33197027328), duration 469, 41/39 MB/s
105: Aug 31 00:57:17 INFO: status: 23% (55264018432/240057409536), sparse 13% (33197334528), duration 527, 42/42 MB/s
105: Aug 31 00:58:13 INFO: status: 24% (57656999936/240057409536), sparse 13% (33213562880), duration 583, 42/42 MB/s
105: Aug 31 00:59:05 INFO: status: 25% (60016099328/240057409536), sparse 13% (33225564160), duration 635, 45/45 MB/s
105: Aug 31 00:59:54 INFO: status: 26% (62432870400/240057409536), sparse 13% (33260052480), duration 684, 49/48 MB/s
105: Aug 31 01:00:53 INFO: status: 27% (64842629120/240057409536), sparse 13% (33424539648), duration 743, 40/38 MB/s
105: Aug 31 01:01:57 INFO: status: 28% (67264446464/240057409536), sparse 13% (33424863232), duration 807, 37/37 MB/s
105: Aug 31 01:02:28 ERROR: VM 105 not running
105: Aug 31 01:02:28 INFO: aborting backup job
105: Aug 31 01:02:28 ERROR: VM 105 not running
105: Aug 31 01:02:29 ERROR: Backup of VM 105 failed - VM 105 not running

EDIT: solution: Change from snapshot backup mode to. Suspand backup mode has solved it.
 
Last edited:
did you investigate the logs in the vm? or on the host? (both would be good)
 
Hey dcsapak thanks for your replay.
Yes i have looked thorugh the Event viewer on the windows server and thare is nothing to see otherwise that is looks like a power outake on the server.
I have also looked thorugh the log on the webinterface but thare is nothing to see.
Where can i find the detailed logs for backup and machine ?

Here you go dietmar i hope this is what you ment thanks !!:

balloon: 2096
bootdisk: ide0
cores: 2
ide0: IMTNodesDiskStorage:105/105-WEB2K3.qcow2,size=233G
ide2: none,media=cdrom
memory: 8096
name: Webserver-2k3
net0: e1000=32:37:64:34:39:63,bridge=vmbr1
numa: 0
onboot: 1
ostype: wxp
smbios1: uuid=b930bb0f-2957-441b-b6d0-b4beb067f7cd
sockets: 1
 
Such error can occur if the qcow2 image has errors. Please check with "qemu-img check ..."
Thank you for the replay. the output was:

qemu-img check /mnt/pve/IMTNodesDiskStorage/images/105/105-WEB2K3.qcow2
No errors were found on the image.
1494932/3662986 = 40.81% allocated, 1.05% fragmented, 0.00% compressed clusters
Image end offset: 97989230592

I have first compressed the server with microsoft disk2vhd tool - then converted the image to qcow2 with qemu-img tool. btw.

The wired thing about this is that it is only every 1 out of 6 backups thats fail's and the VM shuts off
 
Last edited:
We have sometimes at migrated 2003er Server absolutly the same problem. We've tested with a lot of combos with virtual HW (Virtio Disk and NIC, SCSI, SATA, IDE...) But every time the same. But strange, never on the first few backups. We solved it on every VM to suspend at backup. This is working fine.
 
  • Like
Reactions: thomasloldk
We have sometimes at migrated 2003er Server absolutly the same problem. We've tested with a lot of combos with virtual HW (Virtio Disk and NIC, SCSI, SATA, IDE...) But every time the same. But strange, never on the first few backups. We solved it on every VM to suspend at backup. This is working fine.

Thanks gonna edit from snapshot to suspend for the 2003 only.
I hope it works :)

I've mark this post as solved if it will run without fail for the next 7 days :)
 
We have sometimes at migrated 2003er Server absolutly the same problem. We've tested with a lot of combos with virtual HW (Virtio Disk and NIC, SCSI, SATA, IDE...) But every time the same. But strange, never on the first few backups. We solved it on every VM to suspend at backup. This is working fine.

Is has worked. Thanks alot !
 

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!