'Crsi' via qubes-users wrote:
> Do you often reboot your VMs? When Qubes creates a backup of a
running VM it will do the backup using the VM state at startup. So if
for example you started your VM (the ones with the outdated/missing
data) 6 weeks ago, but since starting you added/edited/deleted data and
you create a backup, without restarting the VM, the backup will not
include those changes.
Apparently, no. However, I made sure no VM was running (my host system
crashed previously anyways). That means there's a difference between
powering down a VM (e.g. qvm-shutdown) and having a powered down VM due
to crash / power loss? Am I right that the backup tool uses the LV
Doing a gracefull shutdown or the VM crashing AFAIK is the same in terms
of the backup function as we have discussed. If your VM crashed the
state of the data on disk would still be the same compared to gracefully
shutting down the VM.
Do you still have access to the old system to re-do the backup?
Alternatively if you still have access to the old system you could
manually mount the private volume of the VM and copy the data across.
`vm-<name>-private` for backup only, but my data was in
`vm-<name>-private-snap`?
Then, what about showing a warning that there exists a snap of a VM in
the qubes-backup utility (at the same place where "The VM is running,
backup will contain its state from before its start!" is shown as well),
even if a VM is not running currently? That would have definitively
saved me.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/e947747c-06cf-2920-2c80-2caad6b87d4d%40ak47.co.za.
