4/10/2024 0 Comments Duplicacy preference file![]() If the same command with a clean cache still produces the same error, the next step is to check by hand if those chunks actually exist on the storage. Check the storage if the missing chunk actually exists on the storage For the location of the cache in the web GUI, please refer to Cache usage details. duplicacy/cache under the current repository. The cache is usually located at the directory. The revision file stored in the cache is still the old one and thus may reference some chunks that have already been deleted.įor this reason it is now recommended that the first thing to do when you see the above error is to completely remove the cache directory. This can happen for example when a revision is manually removed from the storage and then a new backup is uploaded with the same revision number. One common cause of missing chunks is a stale cache. If that happens, it is recommended to run the check command instead as it can identify all missing chunks at once for a given snapshot, without any side effects. Some chunks referenced by snapshot test at revision 1 are missingĪll other commands can also report the same missing chunk messages. Sometimes, when you run the check command, it may complain about missing chunks: $ duplicacy checkĬhunk 02c25aea4621acdd4c8751d5ab7ff438fb47308ce8738f030b7db0741c37ecb5 referenced by snapshot test at revision 1 does not exist
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |