Hello!
My basic problem:
I'd like to backup some of my files from AppVMs incrementally with
duplicity. Some of them (vault, ...) don't have network access. I
believe I don't have enough free HDD-space to keep the update within the
AppVM and copy every update to a network-enabled AppVM. (apart from
that, it would take quite long.
My current solution:
Plug in a Thumb-Drive, start first AppVM to be backuped, attach it to
the AppVM, run duplicity, detach thumbdrive, shutdown AppVM, rinse and
repeat with other AppVMs that need to be backuped.
In theory, this should be possible with a script in dom0, but currently
I do it manually. It works fine.
Finally, the thumbdrive is attached to an AppVM with network access and
the whole backup uploaded via sftp. (I want to have a local and off-site
backup anyway, so uploading a huge file isn't that big of a deal for me.)
What I want to achieve:
A virtual block device, which I can attach/detach programatically, so I
don't need to attach a regular thumbdrive.
I've tried to create a virtual blockdevice:
dd if=/dev/zero of=~/backup.img
losetup --find --partscan --show bakup.img
mkfs.fat /dev/loop19
but it doesn't show up in qvm-block -l.
So I don't know weather it's easier to tell qubes "This is a USB
device!" (how?) or tell qubes to attach this loop device to an AppVM.
(Again, how? I was thinking about creating a virtual PCI-device, though
I'd still have to google weather that's possible.)
Sincerely
GammaSQ
--
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/35eb9b31-e10d-01e7-fe5e-59fcabe10a4b%40gmx.at.
For more options, visit https://groups.google.com/d/optout.
