[pYQAJ6Zm]

I rely mostly on Borg backup¹.

1. First, I run it locally on my desktop against a repository I keep on the same drive (/home/backup); then

2. I update, with rsync, a copy of this repository I keep on a dedicated server with full disk encryption; and, finally,

3. I spin up an EC2 instance, mount an S3 bucket with s3ql, and rsync the copy from the previous step up to the one I keep on this bucket.

This process is (embarrassingly) manual.

The backup repository is encrypted with Borg itself, and if I am in need of recovering something I do it from the local copy. I never mount the repository in remote locations.

¹https://github.com/borgbackup/borg

[lfam]

I'm also using borg, to a server I control and also to rsync.net.

Essential and small files like keys (which may be necessary to "bootstrap" the backup in case of complete failure of my workstation) are copied and verified manually to offline storage.

[balladeer]

I also want to have a Borg setup[1] on my personal VPS and backup the "most essential" data (which will be dome docs and some photos - not all) to it along with everything being backed up by CrashPlan. Will explore it someday.

[1] Are there comparable tools which are open source and easier to use (preferably with a GUI or so)?

[gnur]

I basicly do the same, except I sync to google drive using rclone. I also sync to a USB drive about once a week. It basically is a backup of my home dir. the rest of my data already lives in google drive (pictures etc)

[hrez]

Why not "aws s3 sync" for #3?

edit: I see s3ql has many features that can be desirable like compression. How reliable is it?