Of the four methods you list, and their "warts", I would say that duplicity seems the easiest to overcome: "Uses forward snapshots, so recovery takes longer wi

Of the four methods you list, and their "warts", I would say that duplicity seems the easiest to overcome: "Uses forward snapshots, so recovery takes longer with each successive snapshot, unless you upload a "fresh" copy of the data" (unless you have a relatively slow network connection) duplicity will interoperate with plain old SFTP, so we[1] have supported it since it was released. We have also contributed funds to the development of duplicity. In these 10 or so years that it has been around, we've never seen any complaints from customers or evidence of things breaking - it is quite solid. That being said, we do really want to support attic since so many people ask for it. It requires a server-side component to be run, and we try to keep our environment squeaky clean and dead simple[2] - but I think we can cxFreeze it and run it as a binary executable on our end... [1] rsync.net, with HN-readers discount. Just email. [2] There are no interpreters in the jail that each account is locked in, so we can't run a python component on our end.