Linux

I don't. I lose my data like all the cool (read: fool) kids.

Timeshift is a great tool for creating incremental backups. Basically it's a frontend for rsync and it works great. If needed you can also use it in CLI

I use Borg backup with Vorta for a GUI. Hasn't let me down yet.

Is it just me or the backup topic is recurring each few days on [email protected] and [email protected]?

To be on topic as well - I use restic+autorestic combo. Pretty simple, I made repo with small script to generate config for different machines and that's it. Storing between machines and b2.

I have a bash script that backs all my stuff up to my Homeserver with Borg. My servers have cronjobs that run similar scripts.

I use restic (https://restic.net/) which can use rclone to connect to a variety of backends (eg. onedrive, mega, dropbox etc.). Also, resticprofile (https://restic.net/) makes it easier to run (hides flags in the config file). I use it manually but a cron job would be easy to implement (a tutorial is here: https://forum.yunohost.org/t/daily-automated-backups-using-restic/16812).

I like rsnapshot, run from a cron job at various useful intervals. backups are hardlinked and rotated so that eventually the disk usage reaches a very slowly growing steady state.

Pika Backup (GUI for borgbackup) is a great app for backups. It has all the features you might expect from backup software and "just works".

I use Back In Time to backup my important data on an external drive. And for snapshots I use timeshift.

Exactly like you think. Cronjob runs a periodic rsync of a handful of directories under /home. My OS is on a different drive that doesn't get backed up. My configs are in an ansible repository hosted on my home server and backed up the same way.

I do periodic backups of my system from live usb via Borg Backup to a samba share.

Duplicity (cli) with deja-dup (gui) has saved my sorry ass many times.

rsync + backblaze B2. Bafkblaze is stupid cheap.

Cost is about $10 per year.

Used to use Duplicati but it was buggy and would often need manual intervention to repair corruption. I gave up on it.

Now use Restic to Backblaze B2. I've been very happy.

Check out Pika backup. It's a beautiful frontend for Borg. And Borg is the shit.

Kopia or Restic. Both do incremental, deduplicated backups and support many storage services.

Kopia provides UI for end user and has integrated scheduling. Restic is a powerfull cli tool thatlyou build your backup system on, but usually one does not need more than a cron job for that. I use a set of custom systems jobs and generators for my restic backups.

Keep in mind, than backups on local, constantly connected storage is hardly a backup. When the machine fails hard, backups are lost ,together with the original backup. So timeshift alone is not really a solution. Also: test your backups.

I rotate between a few computers. Everything is synced between them with syncthing and they all have automatic btrfs snapshots. So I have several physical points to roll back from.

For a worst case scenario everything is also synced offsite weekly to a pCloud share. I have a little script that mounts it with pcloudfs, encfs and then rsyncs any updates.

I don't, really. I don't have much data that is irreplaceable.

The ones that are get backed up manually to Proton Drive and my NAS (manually via SMB).

BTRFS filesystem, Snapper for taking periodic snapshots and snap-sync for saving one to an external drive every now and then.

BTRFS is what makes everything incremental.

by the way, syncthing is great if you need bi-directional sync.
not exactly what you're looking for (sth like Duplicacy?) but you should probably know about it as it's a great tool.

Restic since 2018, both to locally hosted storage and to remote over ssh. I've "stuff I care about" and "stuff that can be relatively easily replaced" fairly well separated so my filtering rules are not too complicated. I used duplicity for many years before that and afbackup to DLT IV tapes prior to that.

Git projects and system configs are on GitHub (see etckeeper), the reset is synced to my self-hosted Nextcloud instance using their desktop client. There I have periodic backup using Borg for both the files and Nextcloud database.

I use rsync+btrfs snapshot solution.

1. Use rsync to incrementally collect all data into a btrfs subvolume
2. Deduplicate using duperemove
3. Create a read-only snapshot of the subvolume

I don't have a backup server, just an external drive that I only connect during backup.

Deduplication is mediocre, I am still looking for snapshot aware duperemove replacement.

All my devices use Syncthing via Tailscale to get my data to my server.

From there, my server backs up nightly to rsync.net via BorgBackup.

I then have Zabbix monitoring my backups to make sure a daily is always uploaded.

dont keep anything u would be upset to lose /s

timeshift with system files and manually my home folder

I do a periodic backup with Vorta towards my server. The server does a daily backup to an S3 service with Restic

I just run my own nextcloud instance. Everything important is synced to that with the nextcloud desktop client, and the server keeps a month's worth of backups on my NAS via rsync.

Use synching on several devices to replicate data I want to keep backups of. Family photos, journals, important docs, etc. Works perfect and I run a relay node to give back to the community given I am on a unlimited data connection.

DejaDup on one computer. Another is using Syncthing, another I do a manual Grsync. i really should have a better plan. lol

I use btrbk to send btrfs snapshots to a local NAS. Consistent backups with no downtime. The only annoyance (for me at least) is that both send and receive ends must use the same SELinux policy or labels won't match.

I use Rclone which has both an WEBUI and CLI.

At the core it has always been rsync and Cron. Sure I add a NAS and things like rclone+cryptomator to have extra copies of synchronized data (mostly documents and media files) spread around, but it's always rsync+Cron at the core.

Github for projects, Syncthing to my NAS for some config files and that's pretty much it, don't care for the rest.

Setup

Machine A:

• RAIDz1 takes care of single-disk failure
• ZFS doing regular snapshots
• Syncthing replicates the data off-site to Machine B

Machine B:

• RAIDz1 takes care of single-disk failure
• ZFS doing regular snapshots
• Syncthing receiving data from Machine A

Implications

• Any single-disk hardware failure on machine A or B results in no data loss
• Physical destruction of A won't affect B and the other way around
• Any accidentally deleted or changed file can be recovered from a previous snapshot
• Any ZFS corruption at A doesn't affect B because send/recv isn't used. The two filesystems are completely independent
• Any malicious data destruction on A can be recovered from B even if it's replicated via snapshot at B. The reverse is also true. A malicious actor would have to have root access on both A and B in order to destroy the data and the snapshots on both machines to prevent recovery
• Any data destruction caused by Syncthing can be recovered from snapshot at A or B