[PVE-User] Backup off stopped Machines will not work

[Jean R. Franco]

Hi Tobi, 

This is because you have a different fs with this new version. 
You´ll have to modify the VM´s hard disk cache parameter, and change it to write through. 

Best Regards, 


De: "Tobias Guth" <tobias.guth at ecos.de> 
Para: pve-user at pve.proxmox.com 
Enviadas: Quarta-feira, 11 de março de 2015 7:38:45 
Assunto: [PVE-User] Backup off stopped Machines will not work 

Hi, 

since the update of our Proxmox cluster the backup task (snapshot mode) is not able to backup stopped machines anymore. 
I did not found any real good hint on this issue here. Anybody ? 

Thanks and Regards 
Tobi 

Infos -> 

3305: Mar 11 02:10:27 INFO: Starting Backup of VM 3305 (qemu)
3305: Mar 11 02:10:27 INFO: status = stopped
3305: Mar 11 02:10:27 INFO: update VM 3305: -lock backup
3305: Mar 11 02:10:27 INFO: backup mode: stop
3305: Mar 11 02:10:27 INFO: ionice priority: 7
3305: Mar 11 02:10:30 INFO: creating archive '/var/lib/vz/dump/vzdump-qemu-3305-2015_03_11-02_10_27.vma.lzo'
3305: Mar 11 02:10:30 INFO: starting kvm to execute backup task
3305: Mar 11 02:10:32 ERROR: Backup of VM 3305 failed - start failed: command '/usr/bin/kvm -id 3305 -chardev 'socket,id=qmp,path=/var/run/qemu-server/3305.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -vnc unix:/var/run/qemu-server/3305.vnc,x509,password -pidfile /var/run/qemu-server/3305.pid -daemonize -name dmz-srvmail1 -smp '1,sockets=1,cores=1,maxcpus=1' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000' -vga cirrus -cpu kvm64,+lahf_lm,+x2apic,+sep -m 2048 -k de -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:be922e1d5d5e' -drive 'file=/var/lib/vz/template/iso/openSUSE-12.3-NET-x86_64.iso,if=none,id=drive-ide2,media=cdrom,aio=native' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -drive 'file=/var/lib/vz/images/3305/vm-3305-disk-1.qcow2,if=none,id=drive-v
irtio0,format=qcow2,aio=native,cache=none,detect-zeroes=on' -device 'virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap3305i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=C6:59:74:65:46:98,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -S' failed: exit code 1 





pveversion -v 
proxmox-ve-2.6.32: 3.3-147 (running kernel: 3.10.0-7-pve) 
pve-manager: 3.4-1 (running version: 3.4-1/3f2d890e) 
pve-kernel-3.10.0-7-pve: 3.10.0-27 
pve-kernel-2.6.32-37-pve: 2.6.32-147 
pve-kernel-2.6.32-26-pve: 2.6.32-114 
lvm2: 2.02.98-pve4 
clvm: 2.02.98-pve4 
corosync-pve: 1.4.7-1 
openais-pve: 1.1.4-3 
libqb0: 0.11.1-2 
redhat-cluster-pve: 3.2.0-2 
resource-agents-pve: 3.9.2-4 
fence-agents-pve: 4.0.10-2 
pve-cluster: 3.0-16 
qemu-server: 3.3-20 
pve-firmware: 1.1-3 
libpve-common-perl: 3.0-24 
libpve-access-control: 3.0-16 
libpve-storage-perl: 3.0-31 
pve-libspice-server1: 0.12.4-3 
vncterm: 1.1-8 
vzctl: 4.0-1pve6 
vzprocps: 2.0.11-2 
vzquota: 3.1-2 
pve-qemu-kvm: 2.1-12 
ksm-control-daemon: 1.1-1 
glusterfs-client: 3.5.2-1 



_______________________________________________ 
pve-user mailing list 
pve-user at pve.proxmox.com 
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.proxmox.com/pipermail/pve-user/attachments/20150311/4b533d46/attachment.htm>