Sorry I didn't link to an issue but a concern with duplicity is more about its implementation which needs incremental backups to depend on the base full backup

Sorry I didn't link to an issue but a concern with duplicity is more about its implementation which needs incremental backups to depend on the base full backup (that you would make the first time) which means if you want to prune that base backup later on, you need to take a new full backup for later incremental backups to depend on instead of taking continuous incremental backups indefinitely. https://duplicity.gitlab.io/duplicity-web/vers8/duplicity.1.html https://duplicity.gitlab.io/duplicity-web/vers8/duplicity.1.... > When restoring, duplicity applies patches in order, so deleting, for instance, a full backup set may make related incremental backup sets unusable. Other software mentioned have each incremental backups independent of each others, so you can prune any of it and the last one is still retrievable.