[Borgbackup] impossible to mount encrypted repository (via fuse)

[Larry Holding]

It appears your data is inside an encrypted folder inside an encrypted backup. 

Can you provide the output of “borg list /media/veracrypt1/home_repository/backup::lubuntu-2017-10-17-2251” which will show what flies were backed up?


Sent from my toaster. 

> On 21/10/2017, at 09:22, David Luebeck <ldl08 at gmx.net> wrote:
> 
> Dear list,
>  
> I was unable to make mount work with fuse -- and have given up (I have never worked with fuse before).
>  
> So I tried the "borg extract" command, which, surprisingly, also failed -- I am at a loss.
>  
> What I am trying to do is to extract a directory (home/david/Tools/Assertions) and its content to the current location. home/david/Tools/Assertions is a directory that should have been backed up by borg.
>  
> Yet, I get a "Include pattern 'home/david/Tools/Assertions' never matched." comment. May I kindly ask what is going on? How can I verify what files are part of the backup (without using fuse)? Am I misunderstanding the documentation?
>  
> Here is my bash history:
>  
> root at lubuntu:~# cd borg_mp/
> root at lubuntu:~/borg_mp# borg extract /media/veracrypt1/home_repository/backup::lubuntu-2017-10-17-2251 home/david/Tools/Assertions
> Enter passphrase for key /media/veracrypt1/home_repository/backup:
> Include pattern 'home/david/Tools/Assertions' never matched.
> root at lubuntu:~/borg_mp#
>  
> Thanks for your continued help!
>  
> David
>  
>  
> Gesendet: Donnerstag, 19. Oktober 2017 um 20:15 Uhr
> Von: "Thomas Waldmann" <tw at waldmann-edv.de>
> An: borgbackup at python.org
> Betreff: Re: [Borgbackup] impossible to mount encrypted repository (via fuse)
> On 10/19/2017 06:44 PM, ldl08 at gmx.net wrote:
> > Given your earlier hint ("don't use sudo for the mount operation") this
> 
> using root for borg mount and then trying to access that with current
> (non-root) user does not work due to fuse. you need the "allow other"
> option due to that, see "man fuse".
> 
> > seems to suggest that borg backups should not be done as root. Is
> > avoiding root rights therefore 'best practice'?
> 
> best practice (in general, not just with borg) is not to use root when
> you don't need it.
> 
> for backups you will need root, if you want to back up files not
> readable by the current user.
> 
> 
> 
> --
> 
> GPG ID: 9F88FB52FAF7B393
> GPG FP: 6D5B EF9A DD20 7580 5747 B70F 9F88 FB52 FAF7 B393
> 
> _______________________________________________
> Borgbackup mailing list
> Borgbackup at python.org
> https://mail.python.org/mailman/listinfo/borgbackup
>  
>  
> _______________________________________________
> Borgbackup mailing list
> Borgbackup at python.org
> https://mail.python.org/mailman/listinfo/borgbackup
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/borgbackup/attachments/20171021/a159033f/attachment.html>