On 02/21/2017 07:43 AM, Rusty Bird wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi Chris!
On 02/20/2017 08:28 AM, Rusty Bird wrote:
A small qvm-backup wrapper script that handles running VMs by chrooting
into a temporary dom0 filesystem snapshot. The backed up data is the
same as if those VMs had just been killed, which seems to work fine for
the usual journaling/copy-on-write VM filesystems.
https://github.com/rustybird/qubes-stuff/blob/master/dom0/bin/qvm-backup-snap
IIRC, the best practice for backing up is to use a snapshot as the source.
I was thinking that a simple ability to point qvm-backup to a snapshot path
would be optimum for backup flexibility.
I misremembered that as involving a fair amount of refactoring.
Looking into it again right now...
Rusty
There is the issue of handling multiple pools or mountpoints (if they
are configured), but as a personal modification to allow backing-up
while running VMs I'm guessing it should be pretty easy. As long as
everything is on one fs.
Chris
--
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/36ee72eb-5fd1-6d3e-d64d-574e23b98627%40openmailbox.org.
For more options, visit https://groups.google.com/d/optout.
