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
Sync is not backup.
Let's repeat that - sync is not backup.
If your sync job syncs an unintentional deletion, the file is deleted, everywhere.
Backup stores versions of files based on the definitions you provide. A common backup schedule for a home system mat be monthly full, Daily incremental. In this way you have multiple versions of any file that's changed.
With sync you only have replicants of one file that can be lost through the sync.
Now, you could use backup software to a given location, and have that synchronized to remote systems. Syncthing could do this, with the additional safety of "send only" configured, so if a remote destination gets corrupted, it won't sync back to the source.
Edit: as for Pi NAS, I've found Small-Form-Factor desktops to be a better value. They don't have much physical space for drives, but I've been able to use two 3.5" drives or four 2.5" drives in one. My current one idles at <15w.
Or mini pc with one drive. Since you're replicating this data to multiple locations, having local redundancy (e.g. Mirroring) isn't really necessary.
Of course this assumes your net backup requirements are under about 12TB (or whatever the latest single drive size is).
Thank you. Now can you please explain this to my IT department that thinks force syncing everything on our computers to OneDrive is a solution to our lack of backups?
Well, I mean it kind of is a solution. It's a cloud backup solution. OneDrive doesn't just keep a single version of your file, there's versioning, retention policies, etc.
Cloud makes a lot of sense for businesses with small IT staff and a lot of users because while it's not fully in your control, it comes with all the things being discussed here "out of the box" and scales infinitely.
For self hosters there's some fun and power in doing everything yourself, but even then adding cloud as part of your backup (if done securely) is usually a pretty good idea.
You seem to be missing/ignoring that sync will protect against data loss from lost/broken devices. When that happens, those connections are severed with no deletions propagating through them. Not only that, you can configure syncthing to retain older versions for over a year to avoid issues of unwanted edits.
You have to be joking with this. There is no way I'm letting that tracker-filled ransomware near any of my computers.
Simple mirroring doesn't protect against bitrot. RAID 6 does.
You're clearly not suited for giving out advice, so you're getting ignored and blocked. Don't let the door hit you on the way out.
Only if you very carefully architect things to protect against it. I have absolutey seen instances where a drive had a fault and wouldn't mount on the source, and a few hours later a poorly designed backup script saw the empty mount location on the source and deleted the entire backup. You have to be VERY CAREFUL when using a sync system as a backup. I don't use syncthing, but if it can be configured to do incremental backups with versioning then you should absolutely choose that option.
I believe he was talking about a mini PC with a single drive, not Microsoft's "One Drive".
Lots wrong with this statement. The way you protect against bitrot is with block-level checksumming, such as what you get natively with ZFS. You can get bitrot protection with a single drive that way. It can't auto-recover, but it'll catch the error and flag the affected file so you can replace it with a clean copy from another source at your earliest convenience. If you do want it to auto-recover, you simply need any level of redundancy. Mirror, RAIDZ1, RAIDZ2, etc. would all be able to clean the error automatically.