On Thu, Dec 7, 2017 at 11:59 AM, Bernhard <haa...@web.de> wrote:
> On 12/07/2017 03:37 PM, Zrubi wrote:
>> On 12/07/2017 03:04 PM, r...@tuta.io wrote:
>> > Dont tell me the geniuses behind this thought it was more
>> > streamlined to remove the feature and make it only command
>> > line....
>>
>>
>> It was part of the Qubes Manager, so... it is gone with the wind ;)
>>
> I am not really in position to answer this question correctly, but I
> backup "by hand". How that? Well, put uour favourite backup system to
> your computer. A disc to sys-usb for example. Mount it in sys-usb &
> generate a sufficiently large file on it ("truncate -s 200G
> qubes.backup.luks" for example generates a 200G filke in < 1s. If you
> are paranoid you overwrite it with random data).
> (1)  losetup -f                       #   to get a free llop devicename
> I call ip lloopXXX, then
> (2)  losetup /dev/loopXXX   qubes.backup.luks              # now your
> file il looped to /dev/loopXXX, so it "is" a device.
> (3)  cryptsetup  luksFormat   /dev/loopXXX  BACKUP    # Now you create a
> luks volume on it. Check Luks doc for parameters.
> (4)  cryptsetup  luksOpen   /dev/loopXXX  BACKUP       # open it (need
> your pwd once more)
> (5)  mkfs.ext2 /dev/mapper/BACKUP                             # create
> filesystem on the new backup volume
> (6)  mount /dev/mapper/BACKUP    /yourmountpoint.   # and mount it
>
> Now generate one folder in  /yourmountpoint for each qube ; the point is
> that the Q-menu allows to attach any qube's private image to sys-usb as
> well, so you may mount it there to some folder, say /source and then
> rsync your data in the right backup-subfolder. This sound complicated,
> but is really fast to do. At the very end you should
>
> (7) umount     /yourmountpoint           # unmount backup
> (8) cryptsetup  luksClose   BACKUP     # close luks container
> (9) losetup -d   qubes.backup.luks       # free the loop-device
>
> If I were better in bash-scripting I would do that automatedly, but I
> regret that ...    Bernhard

That's way more complex than it needs to be, and also does not provide
integrity protection.

Is there a reason you do not just use qvm-backup?

-- 
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/CABQWM_A%3DpJEe94JZ95x76QNf-TEoSshPp8yu3Eue1vPyX6rEMQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to