Backuppc VS Duplicity

This is a bug in smbclient that leads to corrupted archives being created. There's a Github issue about it. Newer versions of smbclient have a fix. I posted a workaround with a wrapper in the issue if upgrading smbclient is not possible. You could try it out: https://github.com/backuppc/backuppc/issues/404

Go to the Code tab. Click on the green "Code" button. Download as Zip. Or, if you have git installed, consider using git pull https://github.com/backuppc/backuppc instead.

Kind of, though the whole Raku thing made everything a tad wonky.

Some of the nicer Perl software that I use currently is BackupPPC, which has been pretty solid despite the slightly subpar UI: https://github.com/backuppc/backuppc

And another interesting piece that I can think of was RemoteBox, which was pretty niche but still worked nicely: https://remotebox.knobgoblin.org.uk/?page=about

From the more popular packages, one should also mention exiftool, which was written in Perl: https://github.com/exiftool/exiftool

Probably also a lot of other pieces of software, though it doesn't seem like there's much of a large/active community around Perl, for example, have a look at: https://github.com/trending/perl?since=monthly and then compare it to something like: https://github.com/trending/go?since=monthly

http://duplicity.nongnu.org/ at least can use PGP public keys. I've used it for a long time and not seen any particular reason to change.

There are backup tools with built-in encryption like borg backup or duplicity, these should be fine. If you already have a backup process and it's missing encryption then you should be able to use e.g. age or gpg.

For my family photos (critical, irreplaceable, on plex), I use duplicity which can make use of Amazon Glacier and Deep Archive for really cheap storage (0.00099 /gb /month no joke) with incremental versioning and client side encryption. Long restore time, but perfect for disaster recovery on data that doesn't change much. Want to set up the same for music (which rarely but sometimes changes, e.g. Correcting tags).

And google docs / apple cloud etc. aren't proper backups. They can cancel your account, be inaccessible, or hacked even. There's software like duplicity that can upload encrypted backups to multiple services, which are handy. But in any case, if you're doing cloud backups, do do redundant local backups too. My setup is I've a USB stick tacked onto a Raspberry Pi computer, and use something called borg to do daily backups over SSH.

I have had good success using [Duplicity](http://duplicity.nongnu.org/) via [Duply](https://www.duply.net/) for a few years now. The main point for me is that duplicity directly backs up to many cloud-storage endpoints. I'm using google drive specifically, but it supports a ton of options.