[Feature Request] Backup to two different locations with only one .conf file about duplicity-backup.sh HOT 4 OPEN

Thanks for this feature request, I'm not sure yet how easy it would be to implement (I am otherwise pretty busy IRL currently so I didn't have time to look more closely) but this is definitely a good idea and I will look into it as soon as I can.

In the meantime propositions for implementing this and/or pull requests are welcome!

from duplicity-backup.sh.

+1 I have a particular need for this because I have S3 as my offsite backup and I also want the same archive going to a bug-out external USB3.0 hard drive.

The best I can think of is to use duplicity in conjunction with backupninja and have it archive to the hard drive first, then sync that to S3.

from duplicity-backup.sh.

Just stumbled across this request (i know it's a bit old) -

wouldn't the multi:// backend from duplicity be the solution to this request? duplicity(1)
configuring DEST='"multi:///tmp/multiconfig.conf?mode=mirror&onfail=abort'" did work for me for 2 newly created remote-sites (quotation is a bit odd in this case).

Duplicity-backup.sh only needs to be called once - and backs up to 2 different backends (i had one set to local filesystem, and the other to a sftp backend).

from duplicity-backup.sh.

Wow, yes old indeed. That's exactly what I ended up doing. Though, I've since moved to borg, and simply use aws s3 sync to facilitate the syncing from the local backup copy.

from duplicity-backup.sh.