Restic using resticprofile for scheduling and configuring it. I do frequent backups to my NAS and have a second schedule that pushes to Backblaze B2.

I use syncthing to sync files between phone, pc and server.

The server runs proxmox, with a proxmox backup server in VM. A raspberry pi pulls the backups to an usb ssd, and also rclone them to backblaze.

Syncthing is nice. I don’t backup my pc, as it is done by the server. Reinstalling the pc requires almost no preparation, just set up syncthing again

All nextcloud data gets mirrored with rsync to a second drive, so it’s in 3 places, original source and twice on the server

Databases are backed up nightly by webmin to second drive

Then installations, databases etc are sent to backblaze storage with duplicati

I use borgbackup + zabbix for monitoring.

At home, I have all my files get backed up to rsync.net since the price is lower for borg repos.

At work, I have a dedicated backup server running borgbackup that pulls backups from my servers and stores it locally as well as uploading to rsync.net. The local backup means restoring is faster, unless of course that dies.

In short: crontab, rsync, a local and a remote raspberry pi and cryptfs on usb-sticks.

Holy crap. Duplicity is what I’ve been missing my entire life. Thank you for this.

What’s my what lmao?

https://somedaysoon.xyz/posts/tech/backups/

My important data is backed up via Synology DSM Hyper backup to:

• Local external HDD attached via USB.
• Remote to backblaze (costs about $1/month for ~100gb of data)

I also have proxmox backup server backup all the VM/CTs every few hours to the same external HDD used above, however these backups aren’t crucial, it would just be helpful to rebuild if something went down.

For PCs, Daily incremental backups to local storage, daily syncs to my main unRAID server, and weekly off-site copies to a raspberry pi with a large external HDD running at a family member’s place. The unRAID server itself has it’s config backed up to the unRAID servers and all the local docker stores also to the off-site pi. The most important stuff (pictures, recovery phrases, etc) is further backed up in Google drive.

My important data is backed up via Synology DSM Hyper backup to:

• Local external HDD attached via USB.
• Remote to backblaze (costs about $1/month for ~100gb of data)

I also have proxmox backup server backup all the VM/CTs every few hours to the same external HDD used above, however these backups aren’t crucial, it would just be helpful to rebuild if something went down.

Am I the only one using kopia :)?

Im quite new in selfohsting and backups. I went for duplicaty and it is perfect, but heared bad stories and now I use kopia daily backups to another drive and also to B2. Duplicaty is still doing daily backups, but only few important folders to google drive.

Ive heared only good stories about kopia and no one mentioned it

I usually write my own scripts with rsync for backups since I already have my OS installs pretty much automated also with scripts.

I use a Backuppc instance hosted on an off site server with a 1Tb drive. It connects through ssh to all my vms and backups /home and any other folders i may need. It handles full and incremental backups, deduplication, and compression.

I have a central NAS server that hosts all my personal files and shares them (via smb, ssh, syncthing and jellyfin). It also pulls backups from all my local servers and cloud services (google drive, onedrive, dropbox, evernote, mail, calender and contacts, etc.). It runs zfs raid 1 and snapshots every 15 minute. Every night it backs up important files to Backblaze in a US region and azure in a EU region (using restic).

I have a bootstrap procedure in place to do a “clean room recovery” assuming I lost access to all my devices - i only need to remember a tediously long encryption password for a small package containing everything needed to recover from scratch. It is tested every year during Christmas holidays including comparing every single backed and restored file with the original via md5/sha256 comparison.