Hi all,
I'm a bit shocked. I wanted to create a "save" backup where the VM is shut down
and thus all filesystems are in a
consistent state. For that I shut down my VM and then started a backup (backup
mode=stop, compression=lzo) and what must
I see:
INFO: starting new backup job: vzdump 106 --storage local --remove 0 --mode
stop --compress lzo --node pxmx-01
INFO: Starting Backup of VM 106 (qemu)
INFO: status = stopped
INFO: update VM 106: -lock backup
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: VM Name: webserver
INFO: include disk 'scsi0' 'pxmx-ceph:vm-106-disk-2' 8G
INFO: include disk 'scsi1' 'pxmx-ceph:vm-106-disk-1' 32G
INFO: creating archive
'/var/lib/vz/dump/vzdump-qemu-106-2017_11_17-19_02_06.vma.lzo'
INFO: starting kvm to execute backup task
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This makes my question the assumption that the filesystems are in a consistent
state while the backup is created.
Could someone with insight into the backup process explain why kvm is started?
From my POV taking a backup from a
stopped VM only requires to save the VM config and the disk, but no memory (as
it is not running…).
Best,
Uwe
_______________________________________________
pve-user mailing list
pve-user@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
