I notice that Duplicacy creates a cache of file chunks and snapshots in .duplicacy/cache whilst it does a restore operation, presumably it fetches the data here before re-assembling the files?
The cache doesn’t seem to persist, after the restore operation completes there’s only a small handful of files left amounting to a few hundred kilobytes. I was wondering if there is a way to keep all the downloaded chunks, so that any subsequent restore could fetch chunks locally if they are present?
As an example where this could be useful, imagine backing up a large binary file (e.g. 1GB) which changes regularly with small deltas (say 1MB). Now if you wanted to restore different versions of that file, you’d have to redownload the whole 1GB file, but if the chunks had been cached, then you might only need to download one or two chunks when restoring a different version.