I am backing up locally to ZFS volume (so I don’t think it is related to some other posts I saw related to cloud storage providers). I am using duplicacy-util as a wrapper around duplicacy in case that matters.
As part of each backup a prune, and check command is also ran. The check process is returning exit code 100 and thousands of the below lines are written to the log file (obviously with the chunk number differing).
06:02:24 Chunk d4cb825614b7f401fd50a523efc93b4b1fddef7fff0bc595c7342a61025f08e3 referenced by snapshot firewall-local-backup-01 at revision 39 does not exist
This particular backup is revision (snapshot) 39. So it is somewhat strange that something that was just backed is having difficulty finding a chunk.
I did perform a restore of a single (random) file and it worked successfully, but I am not sure if 1 file is a valid test to validate the backup.
Also, the log file contains similar message for revisions starting at 1, skipping to 8, and then similar log files for 8-39. Makes me wonder what was unique for revisions 2-7?
If I try to find one of those chunks on the local disk using the “find” command, no such file exists.
In the prune logs there are lines similar to this:
Deleted fossil 2460eb32016e3c20cda2e72770c16e582319429912de9cb77b8a262dfa6af0d2 (collection 5)
then a bunch of these:
Marked fossil 1b703505f5966b059d7897cc5d63589bd29669f5f9f169754ea314bfdf0bb5ac
and finally this:
Fossil collection 6 saved
Deleted cached snapshot firewall-local-backup-01 at revision 7
Nothing about “exclusive” mode in the prune file.
I am not sure what is causing this, as I have several other backups running that are not doing this. I have tried some of the things listed on the link above that was provided, but I am still getting the massive amount of log about chuks that do not exist.
I do not understand what is happening, or how to fix the error.
Are there any other suggestions on resolving this issue?