23
Centralized backup server (with clients)?
(eviltoast.org)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 03 Jul 2023
23 points (100.0% liked)
Selfhosted
39677 readers
436 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:
-
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!
founded 1 year ago
MODERATORS
There were related github issues open, but not opened by me. It wasn't that borg itself was slow, but it was more to do with the number of files being backed up. Even a simple
find . -type fwould take hours. My problem with it was that borg wouldn't start uploading data until that indexing finished.Restic immediately started uploading while it was still indexing so it cut the overall backup time way down.
If it took 4 hours to index files and then 4 hours to upload those files, borg would total 8 hours while restic was only 4 hours total.
This was something like 10TB and hundreds of millions of files though. I never had an issue with borg on smaller datasets.