Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upAllow backing up running VMs by pausing or snapshotting to enable automatic nightly backups #1239
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
marmarek
Oct 5, 2015
Member
I think this somehow overlaps with #858. Especially when considering creating a backup from inside of VM.
|
I think this somehow overlaps with #858. Especially when considering creating a backup from inside of VM. |
marmarek
added
enhancement
C: core
labels
Oct 5, 2015
marmarek
added this to the Far in the future milestone
Oct 5, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
qubesuser commentedSep 24, 2015
Currently the Qubes backup system cannot back up running VMs since copying a mounted block device would result in arbitrary corruption regardless of journaling.
This is a big shortcoming because it means that it's impossible to setup automatic nightly backup in a way that doesn't negatively affect the user by shutting down all VMs.
However, if the VM is paused, then the block device can be copied in a consistent way, and the state after restoring will be as if the VM had crashed at that moment, which assuming a journaling filesystem is usually an acceptable result.
Pausing is less disruptive than shutting down, but still problematic (kills network connections, pauses computation), so an usually better solution is to take a snapshot of the device and back up the snapshot, although this requires changes in the storage system to allow taking DM snapshots of anything (and potentially requires more storage than pausing).