I’m trying to find a good method of making periodic, incremental backups. I assume that the most minimal approach would be to have a Cronjob run rsync periodically, but I’m curious what other solutions may exist.
I’m interested in both command-line, and GUI solutions.
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.
This is the correct answer.
Is it just me or the backup topic is recurring each few days on !linux@lemmy.ml and !selfhosted@lemmy.world?
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.
It is a critical one. Maybe needs to be part of an FAQ with link to discussion.
It hasn’t succeeded in nagging me to properly back up my data yet, so I think it needs to be discussed even more.
I would argue you need to lose your data once to consider it important over a lot of useless things in your life. Most people are like this.
I have a bash script that backs all my stuff up to my Homeserver with Borg. My servers have cronjobs that run similar scripts.
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 do periodic backups of my system from live usb via Borg Backup to a samba share.
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).
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 really like kopia
I use Back In Time to backup my important data on an external drive. And for snapshots I use timeshift.
Check out Pika backup. It’s a beautiful frontend for Borg. And Borg is the shit.
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.
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.
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.
