glacier_deep_archive_backup VS Duplicacy

If you don't need incremental backups (thus saving space for the signatures) and want to store to S3 Deep Glacier, take a look at https://github.com/mrichtarsky/glacier_deep_archive_backup

Encrypted backup to AWS Glacier Deep Archive ($1/TB/month)

https://github.com/mrichtarsky/glacier_deep_archive_backup

And for ErgodoxEZ:

Compress your keymap so you can add more features without hitting the limit

https://github.com/mrichtarsky/ergodox-compress-keymap

Generate Heatmap from your keypresses so you can see whether your layout is optimal

https://github.com/mrichtarsky/ergodox-heatmap

It's aes256 using openssl:

https://github.com/mrichtarsky/glacier_deep_archive_backup/b...

Does that leak information you would be concerned about?

It's always a full backup.

I have been having great luck with incremental backups with the very similar named Duplicacy https://duplicacy.com/

Pro: No need for a special index database. The chunks are placed in the file system. This explains it in greater detail. Seems to place great emphasis on reliability, which is important for me. Versioning is also supported.

Having all your data in one place isn't wise though, so I am planning on storing encrypted backups on Dropbox and Backblaze B2 using Duplicity so that I am following the 3-2-1 backup rule.

I tried a bunch of different ways but ultimately settled on Duplicacy [0].

It runs inside a Docker container and backs up both my data as well as configurations like my docker compose file and smb.conf.

Off site storage was Backblaze B2, but I moved to Hetzner. Likely will move back just because B2 is cheaper and a bit faster for my region.

Another layer of backup I do is use Duplicacy to backup to a portable hard drive occasionally that I keep off site.

[0] https://duplicacy.com/

Duplicacy

I use Kopia and works well. Have also used this https://duplicacy.com