I've done a manual backup of a KVM VM (Windows) to NFS.
I chose the 'Stop' mode and Gzip compression.
Here's the tail of the log:
1st issue: the log file on the NFS share is zero bytes long. I don't know why it couldn't save it, since the backup file (.gz) is there and is OK.
2nd issue: why does it say 'VM is online again after 2208 seconds' since I could ping it during the compression phase? Doesn't the 'Stop' method stop the VM, snapshot it, start it and then compress and upload the backup? It should have been offline only for a few seconds (shutdown, snapshot and bootup), right, or am I missing something?
I chose the 'Stop' mode and Gzip compression.
Here's the tail of the log:
Code:
INFO: status: 100% (161061273600/161061273600), sparse 78% (127045570560), duration 2178, read/write 456/0 MB/s
INFO: transferred 161061 MB in 2178 seconds (73 MB/s)
INFO: archive file size: 10.27GB
INFO: vm is online again after 2208 seconds
INFO: Finished Backup of VM 100 (00:36:49)
cp: cannot create regular file '/mnt/pve/nas1-storage2/dump/vzdump-qemu-100-2017_11_24-11_02_17.log': Operation not permitted
INFO: Backup job finished successfully
TASK OK
1st issue: the log file on the NFS share is zero bytes long. I don't know why it couldn't save it, since the backup file (.gz) is there and is OK.
2nd issue: why does it say 'VM is online again after 2208 seconds' since I could ping it during the compression phase? Doesn't the 'Stop' method stop the VM, snapshot it, start it and then compress and upload the backup? It should have been offline only for a few seconds (shutdown, snapshot and bootup), right, or am I missing something?