Proxmox backs up the VMs -> backups are uploaded to the cloud.
Cronjobs and rclone have been enough for me for the past year or so. Interestingly, I've only needed to restore from a backup once after a broken update. It felt great fixing that problem so easily.
I have 2 servers that backup to each other. I also use B2 for photos and important stuff.
Almost all the services I host run in docker container (or userland systemd services). What I back up are sqlite databases containing the config or plain data. Every day, my NAS rsyncs the db from my server onto its local storage, and I have Hyper Backup backup the backups into an encrypted S3 bucket. HB keeps the last n versions, and manages their lifecycle. It's all pretty handy!
My home servers a windows box so I use Backblaze which has unlimited storage for a reasonable fixed price. Have around 11TB backed up. Pay the extra few dollars for the extended 12 month retention of deleted files, which has saved me a few times when I needed to restore a file I couldn’t find.
Locally I run stablebit DrivePool and content is mirrored and pooled using that, which covers me for drive failures.
I’m backing up my stuff over to Storj DCS (basically S3 but distributed over several regions) and it’s been working like a charm for the better part of a year. Quite cheap as well, similar to Backblaze.
For me the upside was I could prepay with crypto and not use any credit card.
I've recently begun using duplicati to backup the data from my docker containers and VMware snapshots for the guest VM itself, just currently struggling to understand how to automate the snapshots yet so I do them manually
TrueNAS zfs snapshots, and then a weekly Cron rsync to a servarica VPS with unlimited expanding storage.
If you use a VPS as a backup target, you can also format it with ZFS and use replication. Sending snapshots is faster than using file-level backup tool, especially with a lot of small files.
Interesting, I have noticed it's very slow with initial backups. So snapshot replication sends one large file? What if you want to recover individual files?
Kopia to Backblaze B2 is what I generally use for off-site backups of my devices. Borg's another good option to look at, but not as friction-less in my experience. There are a couple of additional features that are available in Kopia that are nice to have and are not in Borg (i.e. error correction, file de-duplication) from what I recall. edit: borg does do de-duplication
rsync + borg, but looking at bupstash
Using ESXi as a hypervisor , so I rely on Veeam. I have copy jobs to take it from local to an external + a copy up to the cloud.
I run everything in containers, so I rsync my entire docker directory to my NAS, which in turn backs it up to the cloud.
rsnapshot
A simple script using duplicity to FTP data on my private website with infinite storage. I can't say if it's good or not. It's my first time doing it.
ZFS array using striping and parity. Daily snapshots get backed up to another machine on the network. 2 external hard drives with mirrors of the backup rotate between my home and office weekly-ish.
I can lose 2 hard drives from the array at the same time without suffering data loss. Any accidentally deleted files can be restored from a snapshot if my house is hit by a meteor I lose maximum of 3-4 days of snapshots.
I have an rsync script that pulls a backup every night from my truenas server to my Synology.
I've been thinking about setting up something with rsync.net so I have a cloud copy of my most important files.
dont overthink it.. servers/workstations rsync to a nas, then sync that nas to another nas offsite.
Compressed pg_dump
rsync’ed to off-site server.
Veeam backup and recovery notnfor retail license covers up to 10 workloads. I then s3 offsite to backblaze
Zfs z2 pool . Not a perfect backup, but it covers disk failure (already lost one disk with no data loss), and accidental file deletion. I'm vulnerable to my house burning down, but overall I sleep well enough.
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
If you are using kubernetes, you can use longhorn to provision PVCs. It offers easy S3 backup along with snapshots. It has saved me a few times.
All my backups are in /home/Ryan/Documents. Please don't break my Minecraft server.
Running a Duplicacy container backing up to Google drive for some stuff and Backblaze for mostly all other data. Been using it for a couple years with no issues. The GUI and scheduling is really nice too.
- kopia backup to 2nd disk
- kopia backup to B2 cloud
- duplicaty backup to google drive (only most important folder <1GB)
Most of the files are actually nextcloud so I get one more copy of files (not backup) on PC by syncing with nextcloud app
I use Bacula to an external drive, it was a pain in the ass to configure but once it's running its super reliable and easily extended to other drives or folders
Not what you mean but I use BDR shadow protect and Datto. Depending on customers budget.
For my webserver, mysqldump to a secured folder, then restic backup the whole /svr folder, then rsync the restic backup to another server. Also have a system that emails me if these things don't happen daily. The log files are uploaded to a url, the log file is checked for simple errors, and if no file is uploaded in time, email.
Of course, in my case, the url files are uploaded to - and the email server... are the same server I'm backing up... but at least if that becomes a problem, I probably only need the backups I've already made to my second server.
My server is a DiskStation, so I use HyperBackup to do an encrypted backup of the important data to their Synology C2 service every night.
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!