I have a home server that I’m using and hosting files on it. I’m worried about it breaking and loosing access to the files. So what method do you use to backup everything?
You must log in or register to comment.
Backblaze on a B2 account. 0.005$ per gb. You pay for the storage you use. You pay for when you need to download your backup.
On my truenas server, it’s easy as pie to setup and easy as 🥧 to restore a backup when needed.
I’ll add to this that restic works amazingly with Backblaze. Plus a dozen or so other backup options.
B2 is awesome. I have Duplicati set up on OpenMediaVault to backup my OS nightly to B2 (as well as a local copy to the HDD).
Maybe I’m stupid, but what is B2? A Backblaze product?
Yes it’s their cloud storage.
I didn’t realize they did anything other than that!
I think they had some form of cloud computing at some point but they now focus on B2 and some backup tools that utilize B2.
deleted by creator
I also recommend B2, it’s an S3 compatible service so any backup software/scripts/plugins that work with S3 should work with Backblaze.
You guys back up your server?
In the 20 years that I’ve been running a home server I’ve never had anything more than a failed disk in the array which didn’t cause any data loss.
I do have backups since it’s a good practice and also because it familiarizes me with the software and processes as they change and update so my skillset is always fresh for work purposes.
Borgbackup
Autorestic, nice wrapper for restic.
Data goes from one server to second server, and vice versa (different provider, different geolocation). And to backblaze B2 - as far as I know cheapest s3-like storage
Wasabi might also be worth mentioning, a while back I compared S3-compatible storage providers and found them to be cheaper for volumes >1TB. They now seem to be slightly more expensive (5.99$ vs. 5$), but they don’t charge for download traffic.
Borgbackup to Borgbase
cronjobs with rsync to a Synology NAS and then to Synology’s cloud backup.
On hope
This is the way.
This guy is rawdogging his RPi, just like me
Me too! Actual servers are docker-compose which is on git but the data…yeah that’s on hope hahaha
And using the fact that raid is a backup!
ITT: lots of the usual paranoid overkill. If you do
rsyncwith the--backupswitch to a remote box or a VPS, that will cover all bases in the real world. The probability of losing anything is close to 0.The more serious risk is discovering that something broke 3 weeks ago and the backups were not happening. So you need to make sure you are getting some kind of notification when the script completes successfully.
While I don’t agree that using something like restic is overkill you are very right that backup proess monitoring is very overlooked. And recovering with the backup system of your choice is too.
I let my jenkins run the backup jobs as I have it running anyways for development tasks. When a job fails it notifies me immediately via email and I can also manually check in the web ui how the backup went.
Various different ways for various different types of files.
Anything important is shared between my desktop PC’s, servers and my phone through Syncthing. Those syncthing folders are all also shared with two separate servers (in two separate locations) with hourly, daily, weekly, monthly volume snapshotting. Think your financial administration, work files, anything you produce, write, your main music collection, etc… It’s also a great way to keep your music in sync between your desktop PC and your phone.
Servers have their configuration files, /etc, /var/log, /root, etc… rsynced every 15 minutes to the same two backup servers, also to snapshotted volumes. That way, should any one server burn down, I can rebuild it in a trivial amount of time. This also goes for user profiles, document directories, ProgramData, and anything non-synced on windows PC’s.
Specific data sets, like database backups, repositories and such are also generally rsynced regularly, some to snapshotted volumes, some to regulars, depending on the size and volatility of the data.
Bigger file shares, like movies, tv-shows, etc… I don’t backup, but they’re stored on a distributed GlusterFS, so if any one server goes down, that doesn’t lose me everything just yet.
Hardware will fail, sooner or later. You should see any one device as essentially disposable, and have anything of worth synced and archived automatically.
Restic to multiple repositories, local and remote.
I have everything in its own VM, and Proxmox has a pretty awesome built in backup feature. Three different backups (one night is to my NAS, next night to an on-site external, next night to an external that’s swapped out with one at work - weekly). I don’t backup the Proxmox host because reinstalling it should it die completely is not a big deal. The VM’s are the important part.
I have a mini PC I use to spot check VM backups once a month (full restore on its own network, check its working, delete the VM after).
My Plex NAS only backs up the movies I really care about (everything else I can “re-rip from my DVD collection”).
3-2-1
Three copies. The data on your server.
-
Buy a giant external drive and back up to that.
-
Off site. Backblaze is very nice
How to get your data around? Free file sync is nice.
Veeeam community version may help you too
I’m not sure how you understand the 3-2-1 rule given how you explained it, even though you’re stating the right stuff (I’m confused about your numbered list…) so just for reference for people reading that, it means that your backups need to be on:
- 3 copies
- 2 mediums
- 1 offsite location
Huh. I always heard 3 copies, 2 locations, 1 of the locations offsite. Yours makes sense though.
-
Borgbackup to cloud storage on rsync.net
I use proxmox server and proxmox backup server (in a VM 🫣) to do encrypted backups.
A raspberry pi has ssh access to PBS and it rsync all the files, and then uploads them to backblaze using rclone.
https://2.5admins.com/ recommended “pull” backups, so if someone hacks your server they don’t have access to your backups. If the pi is hacked it can mess with everything, but the idea is that is has a smaller attack surface (just ssh).
PS. If you rclone a lot of files to backblaze use https://rclone.org/docs/#fast-list , or else it will get expensive
restic backup to Azure and Backblaze
