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:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
I think you're asking about the Samba share? If it works, there's no real downside except the speed and general wonkiness of the SMB protocol.
As I would rank the different options:
This is really helpful thank you! I think it's samba share? Whatever Unraid has just baked in and calls "shares".
Googling rsync that looks like it'll work, and faster is better!
While I do want true backups of a few drives (as in: if a drive fails, restore the backup to a new drive, physically swap it out, and you're good to go), the majority of the data I'm just looking to have it "backed up" (as in: all of the files are present in more than one location). The majority of the data is ~18TB of media for my plex server. My unraid is: 1x 2TB, 1x 10TB, 1x20TB and 1x20TB(parity). It sounds like Rsync-ing the 20TB drive with my plex media and the 20TB unraid disk would get me what I need?
Thanks for the pointers, getting a few things to google is incredibly helpful.
SMB isn't really all that slow these days.
I have NFS and SMB shares set up (same directory) and copying files to/from them maxes out my gigabit LAN.
SSH on the other hand is slower, because there's more CPU overhead.
All data and benchmarks would disagree with you. If you find something showing that SMB isn't slower than the others mentioned, I'd love to see it.
I disagree with the other person, rsync + ssh is faster even in my own benchmarks. But samba is plenty fast enough these days, I can easily have it max out my gigabit network so I don't need anything faster. So for me (and I would guess the majority of people) speed really isn't a concern anymore, so I use samba because it's easy to use and it makes sharing network folders to anything else a breeze.
It's like phones. Yeah technically the newest iPhone is faster than this years budget Samsung. But when's the last time your phone was actually a bottleneck? (Unless you're one of those people who play games, in which case, actually please respond cause I could use some really nice idle city builders for my phone pls)
Real world usage tells me all I need to know.
Well for sure that is better than nothing, so since you have it keep doing it until/unless you have something better.
Your next task is to make sure you can restore the data. Since the data is - probably - saved, you have good odds. Practice restoring means that when a computer breaks you will faster be able to get the replacement running again. Practice also means in the off chance something isn't saved you find out about it while your old computer is still running.
Then we need to think about threats.
Ransomware that encrypts your disk will encrypt that shared drive too. I don't know what unraid offers, but you should enable read-only snapshots (now practice restoring them!), and save those snapshots. Ideally you want some pattern like all backups for a week, then 1 backup a week for a month, then 1 backup a month for a year, and 1 backup a year for the next 7 years. This way you can just go back to before the ransomware and restore from backups.
You might delete one file on accident. You are likely not to realize it for a while. One more reason for the pattern saved above. Make sure you can restore individual files.
Your house might burn down destroying all computers. You want a copy of all that data someplace else, maybe more than one someplace elses. Though perhaps you only want a yearly and weekly copy. If the data is encrypted (very good idea for off site!) make sure the key is saved someplace else secure where you can find it - a key you can remember is a bad key so thought about how to save the key is important.
You might die or become mentally disabled with important files that your heirs need. Pictures, wills, tax/bank data (including passwords!). document the above well enough that someone else can at least figure it out. Ideally you would know someone unrelated to you into computers and leave them a lot of money ($5000?) to figure out your system and get your heirs the important files after you die. (this should be a great business opportunity, but odds are not enough people will pay for it)
There are a lot of variations I didn't think of, but I think I covered enough to start you out. You get to decide how far you go. I'm not far enough myself, but at least I have one backup in my RAID.
One last thought - you might have some data you don't want backed up. If you delete the evidence of your crime but the backups are there they can get you. Your secret porn collection might be legal, but still not something you want your heirs to find out about, maybe keep it in a different way? Your call here.
So I had questions on practicing restore! I wanted to start by just making sure I had something, but how does one validate, short of having a duplicate hardware setup to restore to?
Some of this is a bit extreme but a lot of it is capabilities I'll be slowly building up. Read only backups is a fantastic point. I am indeed working at offsite backups. I have a separate drive for all the "untimely exit" stuff, and, most importantly, a physical printed folder in a fireproof safe. I have had/have some health issues that make it relevant. I strongly encourage practicality of air-tight security there. A plain text with accounts and passwords is a bad idea, but plain text naming where accounts are is reasonable. Yes, there's always social engineering, but the people at those firms should be looking for proper legal documentation from the executor of the estate, and 98% of people are more likely to have a loved one who is cleaning things up than have someone stealing their identity. There is so much to handle when someone passes, any impediment makes it more likely someone just brute forces things.
Re: Scrubbing "impolite" data. I lost someone last fall who was a data nut (tons of personal and professional videos and photos). We joked about finding their porn stash, but mostly we got drunk clicked around, and laughed at them flubbing a take at a work video, I cried a bit at a motorcycle maintenance list they never got to, that kind of thing. End of life is messy and gross. If it doesn't carry jail time I can promise you no one will care whats on the computer after cleaning the endless bodily fluids out of the bed and carpet.
I may pattern the backups of some drives, but there's no way I'm going to have enough space to do that for 20+ TB of media. I like my media archive, I've spent a long time building it, but having the main drive, the local backup in a RAID, and an offsite is probably where that will end. The offsite will probably be a monthly one so that should help.
On the other hand, I am working on cool genealogy project through gramps, which is intended to be a "forever archive" kind of thing. That I may pattern as the data would be incredibly difficult to replace and there's an increased chance of non-malicious issues given I'll be opening it up to extended family of varying technical expertise. THAT I may pattern more extensively the way you suggest.
Validating restore is one of the harder things. There are some people who restore means it works on the exact same hardware - commonly hardware vendors will change internal details without changing model numbers so this plan often fails when it turns out the computer restore to is slightly different and so you don't have the right driver on your backup (My dad used to repair computers for people who did this - he often charged thousands of dollars to fix a 10-30 year old machine that a new PC could run circles around. IIRC most of the machines were HPUX and not PCs so the cost of porting to a new machine was ). Most people figure they will be replacing the computer with something newer and so instead install the latest OS and then restore just files, now you face the question of do you restore applications or not?
I would test restore on a cheap raspberry-pi, assuming the backup is from x86, or on a cheap ebay x86 if the backup is from ARM. For most self hosted people this is really what they want to know can be done because they don't know what the replacement hardware will be. The goal here isn't a usable system, it is enough that you can show your files still exist.
I don't know why I didn't think of that! I have a number of pis and a few outdated mini-pcs. I didn't connect that fact they can be miserable to use so long as it validates it works. Thank you so much!