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 # 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.
I also recommend B2, it’s an S3 compatible service so any backup software/scripts/plugins that work with S3 should work with Backblaze.
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.
They always had a personal backup product for windows. I use it to back up almost 2 TB of files on my desktop PC for a flat rate. It’s pretty convenient because it’s almost fully set & forget.
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).
On hope
The “small to medium business” route I see!
And using the fact that raid is a backup!
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
This is the way.
You guys back up your server?
If your data is replaceable, there’s not much point unless it’s a long wait or high cost to get it back. It’s why I don’t have many backups.
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
Borgbackup to Borgbase
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 process 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.
deleted by creator
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
-
Restic to b2. Works great. I’ve also used duplicati in the past to b2 as well.
Same setup here. I’ve got a really basic script running nightly from cron. B2 is cheap as, and having an encrypted backup that’s versioned is great for piece of mind.
At one point I was away from home and my (little rpi) server wasn’t accessible, but with the restic repo up on B2 I was able to easily find a file I urgently needed remotely. It’s awesome.
cronjobs with rsync to a Synology NAS and then to Synology’s cloud backup.
Proxmox Backup Server. It’s life-changing. I back up every night and I can’t tell you the number of times I’ve completely messed something up only to revert it in a matter of minutes to the nightly backup. You need a separate machine running it–something that kept me from doing it for the longest time–but it is 100% worth it.
I back that up to Backblaze B2 (using Duplicati currently, but I’m going to switch to Kopia), but thankfully I haven’t had to use that, yet.
PBS backs up the host as well, right? Shame Veeam won’t add Proxmox support. I really only backup my VMs and some basic configs
Veeam has been pretty good for my HyperV VMs, but I do wish I could find something a bit better. I’ve been hearing a lot about Proxmox lately. I wonder if it’s worth switching to. I’m a MS guy myself so I just used what I know.
Veeam can’t backup Proxmox on hypervisor level, only HyperV and VMWare
PBS only backs up the VMs and containers, not the host. That being said, the Proxmox host is super-easy to install and the VMs and containers all carry over, even if you, for example, botch an upgrade (ask me how I know…)
Then what’s the purpose over just setting up the built in snapshot backup tool, that unlike PBS can natively back up onto an SMB network share?
I’m not super familiar with how snapshots work, but that seems like a good solution. As I remember, what pushed me to PBS was the ability to make incremental backups to keep them from eating up storage space, which I’m not sure is possible with just the snapshots in Proxmox. I could be wrong, though.
You are right about the snapshots yeah. The built in backup doesn’t seem to do incremental backups.
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.
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”).
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.
