Resume after subsequent backup

Support
#1

Hi, according to this thread Duplicacy Issue: Is backup pause / resume supported? duplicacy cannot pause and resume itself/ checkpoint itself basically if it is not an initial backup. Please do correct me if I’m wrong, but it seems this would be an issue when I do subsequent backups, if I’m only able to run backups overnight for multiple GBs to cloud, because there might not be enough time for completion.

It is an open issue #363 on github, and there is a script mentioning it in a short-term to do list. Is there a workaround towards this issue currently, or may I know if an update towards this is currently under way?

Thanks.

#2

Right, Duplicacy doesn’t save an incomplete file if a subsequent backup gets interrupted. However, the next backup will be able to correctly skip chunks that have already been uploaded, which means it is still a fast resume, although not as fast as if there is an incomplete file.

A workaround (especially if you suddenly have added a large amount of files to an existing backup) is to change the repository/backup id and then the next backup becomes an initial backup.