-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
borg mount for easy restores #103
Comments
Maybe look into this in rl? |
Ok, we do in version 1:
|
Hello, Greetings, |
@henfri this is somehow "pie in the sky", especially if there is no idea how to in fact implement that (and also considering the limited developer resources we have for this). |
Maybe I do overlook the complexity, but I thought of: |
mount is potentially expensive (when mounting a single archive or with versions view), so not quite as quick as one would expect for a slider dragged by mouse. also, what's the use case? if you search for a specific version of a file, the versions view is better and you don't need a slider then anyway. |
This shows the usecase quite well: I am open for other suggestions. But browsing an archive for the version of the file that was 'still ok' without knowing when it went bad today is not very nice. |
borg 1.1 mount's versions view is best to find a specific version of a file, without umounting / mounting all the time. |
I liked a lot this approach on https://github.com/bup/bup/blob/master/Documentation/bup-web.md |
@pedro-nonfree not sure I like that:
Exposing a "borg mount" via samba seems more appropriate, but even there we still have an ACL issue (besides the usual uid/gid mapping issues). |
by default localhost:8080, but putting 0.0.0.0:8080 is dangerous yes, as it says: https://github.com/bup/bup/blob/master/Documentation/bup-web.md (but you can listening on a particular interface where only for a particular restricted LAN, VLAN, VPN) I didn't try borgweb yet, if it has auth, less problems on exposing stuff
I see it handy for a quick browsing experience (to see what's the path for the recovery for example, what snapshots I have, what files I stored), or to just download one or two files (and/or do a fast preview of file). In that cases content is more important than ACL stuff tried
so meanwhile/right now, after mounting burp backup I can do: I'm just sharing what is useful for me. |
not a daily task, but it may happen if the admin is away and it would be nice if users could help themselves: restore some files they lost / they want to restore to an earlier version.
borg mount offers quite easy access for users who can access it and deal with a file manager or other tools to locate the data they want.
access / permissions need to be carefully dealt with - likely a user should not get access to files they usually would not be able to access.
same-system borg mount - uid/gid/permissions apply (but ACLs are not implemented via FUSE).
different-system borg mount - difficult, uid/gid often does not match.
so, guess the easiest thing that could work is an optional mount/unmount button that just executes a pre-configured mount / unmount command.
Note: borg mount locks the repo, so it can't be mounted permanently.
The text was updated successfully, but these errors were encountered: