46
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 07 Jul 2024
46 points (97.9% liked)
Selfhosted
40198 readers
460 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
I'm going to argue that, yeah, probably, but it depends.
Are you at risk of just losing your personal data, or is this hosting services other people upload shit to?
If you've got other people's photos or documents or passwords or whatever, then no. You need more than one backup, you need to automate testing of your backups, and you need to make damn sure that you can absolutely recover from BOTH sets of backups.
If it's just your shit, then you do what you're comfortable with: if you lost your home server and it's backups, then are you okay with that outcome?
If that's a 'no', then you need more than the one backup, and testing, and automation blah blah blah.
I have the live server data, archives on a different drive in the system, and archives uploaded to the cloud.
About once a week or so I burn the local backup files to a BD-R, chuck that in a media-rated fire safe (an aside: a paper-rated fire safe is not sufficient for plastic disks, so make sure you buy one that actually will keep your backups from being melted otherwise, meh, you didn't really do anything).
The cloud versions are on a provider that claims 99.99999% durability, which is good enough, and I keep 60 days of backups in the cloud so that I have enough versions to rotate back through.
I also built a 2nd little baby server that'll grab the backups and do an automated restore and stand up my entire stack once a month, just to verify that the backup archives are actually backups and actually can be downloaded, unarchived, and automatically bring up all the stacks and populate the databases and have everything just appear up and running.