this post was submitted on 04 Nov 2023
80 points (92.6% liked)

Selfhosted

39997 readers
882 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
ruud
Loki
CannaVet
devve
HybridSarcasm
[email protected]
80
What I just learned about restoring BorgBackups (github.com)
submitted 1 year ago by [email protected] to c/selfhosted
20 comments fedilink hide all child comments
 

Maybe I state the obvious here but anyway:

Tonight I found a super comfi way to browse and restore data from Borg repositories. In vorta you can add any existing borg repository and mount the containing backups in a very functional GUI. Until now I somehow assumed you could only deal with backups created in vorta which is not true.

For context let me explain why I find that so useful: I am using a wonderful Borg / Borgmatic container from the borgmatic collective. It works super reliable. But for restoring files you have to mount the backup in the container and deal with the files inside the container. This can be difficult i.e. when looking for a specific file in a folder with a lot of files (like a foto collection where you accidentally deleted one file).

If any Borg users are out there: I would be interested what your workflows look like.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 13 points 1 year ago (1 children)

Nice frontend, but honestly the Borg CLI and borgmatic config is so easy and straightforward to use, you shouldn't need any GUI.

May I ask why you are running Borg inside a container? You could just run it directly on the host and that would've solved your problem it seems.

[–] [email protected] 4 points 1 year ago (1 children)

Borg is running on a headless server. Everything is dockerized, so I did the same with Borg. Advantages are that the setup is easy to setup, backup the config and move it to a different server. At first I did not realize that the mount of the backup only exists in the container and that this is making things a little harder.

[–] [email protected] 1 points 1 year ago (1 children)

Could you mount a blank directory into docker, then use borg to mount the backups into that?

[–] [email protected] 1 points 1 year ago

This was the first idea. I cannot explain very well why this does not work. But I think the issue is that the borg mount magic lives inside the container so the filesystem cannot be seen from the host. You can mount an empty directory and copy the files you want to access from the host into it. Problem with that is that you are stuck with the tooling provided by the container.