Good to hear! And that makes sense if the provider’s upload tool was automatically splitting files larger than a certain size into chunks for the upload.
It’s possible to have dblock files smaller than your volume size (in this case 200MB) such as at the end of a backup when there’s not a full volume’s worth of data left to upload or after a compacting operation when multiple “small” files are re-compressed into a single larger one.
However, those files should still be recorded in the local Duplicati databse so if an unexpected remote dblock file is found the most likely reasons include:
- upload failed but destination didn’t delete the partial file
- upload succeeded but Duplicati didn’t record it in the local database for some reason
- multiple backups are pointing to the same destination folder
I don’t know how they handle cold storage so I suppose it’s also possible a file that Duplicati used to use and deleted (likely due to version control or compacting) never got removed out of cold storage and has somehow been moved to live again…
One way to try and narrow this down might be to use the
--log-level parameters to store a detailed log file of the backup. If the error happens again, look at the previous log file for the name of the “unexpected” dblock. If it’s there then there should also be record of it being saved into the local database.