Selfhosted
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:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
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.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
borgmatic dev here. First of all, if Vorta is working well for you to recover files, then by all means use Vorta! Right tool for the job and all. Having said that, a couple of thoughts on using borgmatic in Docker and recovering files:
borgmatic has a search feature that makes finding a particular file in an archive or across archives pretty easy. So that might be step one in restoring an accidentally deleted file.
Once you've found the file and archive to restore, you can either use
borgmatic extractorborgmatic mount. Withextract, you copy one or more files out of a backup archives. The challenge though is that with borgmatic in a container, by default there's not an easy way to copy those files into their original locations. However I think the "fix" is to mount your source volumes as read-write instead of (the documented) read-only. That way you can easily copy extracted files back to where they belong.As for
borgmatic mount, you've got a similar challenge and fix. You can presumably mount backup archives (or a whole repository) within the container, but then you need to copy your recovered files out of that mount into their original source volumes. So that probably also means those volumes need to be mounted read-write.Let me know if you have any questions!
Thanks for your answer and taking the time! Borgmatic search I did not know. That is an amazing tool. You are right about the mounting. My way of dealing with that is a NFS share I mount RW so I can restore to that and than copy whereever. This might it be ideal for very large restores though. Initially I thought I could borgmount to the NFS share and then access the filesystem via NFS. But this does nof work I suppose as Borg only lives inside the container. Generally I do like having Borg and Borgmatic containerized as almost everything else I selfhost but it adds complexity restoring. Anyways great project, it is just so powerful and in many ways elegant. Really enjoy using it!
Glad to hear it's (mostly) working out for you! I know you came here looking for best practices with restores, but if you end up coming up with anything yourself, feel free to comment on that Docker borgmatic ticket with requests or ideas. I use the container myself on some systems for the same reasons you do, and I also wouldn't mind smoother restores!
Is there a way to have an ssh remote without borg installed on the target?
Nope! Borg always requires Borg on the remote side. It's Borg's biggest strength and weakness versus competing backup systems IMO. Strength, because it can do pretty smart stuff with its own code running on both sides. Weakness, because it means it doesn't work natively with cloud object storage like S3. It's a tradeoff like anything else.
Makes sense - compromises like you say.
So in the context of unraid, do I just run the borgmatic container on both ends? Or should there be a specific 'server' one?
EDIT: I found borgserver. I'm pretty sure that's the correct one to use.
I'm not super familiar with Unraid, but yeah, the borgserver image sounds like it'd work for this.. You don't need borgmatic on the server side unless you want it there to make running Borg commands easier.
Is it normal for borg to nag for my password so many times?
Context: I have 2 config files, as I would prefer to have each app I want backed up in a separate config if reasonable. I don't have a remote setup yet - it's just using a local repository.
Separate configs is totally reasonable. It just sounds like you haven't configured your Borg passphrase with borgmatic.. Otherwise it wouldn't prompt for your passphrase at all.
I missed that part in the docs - thanks. Now it's working way better. Thanks heaps - I'm going to trial this alongside my duplicati for a bit (as I've heard a few too many horror stories about duplicati...)
I hope one (or both!) of them end up working out for you.
You could always sftp mount the repo if you cant install borg but have sftp support. Probably won't be as efficient though.