See also the follwoing output
I hope it is bug, but my guess is that vzdump switches to "stop mode" because the container is stopped already?
But why? If I want to do a 100% clean backup by shutting down the container first, wouldn't it be still useful (and fast) to use the snapshot mode. This way the container could be started again very quickly.
Code:
[root@myserver ~]# vzdump --snapshot 101 --tmpdir /tmp --dumpdir /root
INFO: starting new backup job: vzdump --snapshot 101 --tmpdir /tmp --dumpdir /root
INFO: Starting Backup of VM 101 (openvz)
INFO: CTID 101 exist unmounted down
INFO: status = CTID 101 exist unmounted down
INFO: backup mode: stop
I hope it is bug, but my guess is that vzdump switches to "stop mode" because the container is stopped already?
But why? If I want to do a 100% clean backup by shutting down the container first, wouldn't it be still useful (and fast) to use the snapshot mode. This way the container could be started again very quickly.