![]() ![]() the oldest snapshots) were referencing the missing chunks. I then ran the Check command and found out that the first few (i.e. I checked the storage and the missing chunk does not exist. It does not tell me much except that it was deleted under -exclusive mode as you guessed. I found the log file where it was deleted. ![]() This missing chunk is very likely to be the result of running the prune command with the -exclusive while another backup was running. Remember that no other backup can be running when you run this command (due to the use of -exclusive). To correct the state of the storage, you need to find out which snapshots reference this missing chunk by running the check command, and then manually remove these snapshot files from the storage.Īfter that, run duplicacy prune -exclusive -exhaustive to clean up the storage. Of course first double check the chunk doesn't exist in the storage, otherwise it is a different issue. You may be able to find out when this chunk was deleted from these logs files. I looked in the docs, but I could not find any information about what I need to do to solve it. All the snapshots which should be deleted are still on the storage location. I run the following command:ĭuplicacy prune -a -storage default -keep 0:14 -keep 1:3 -exclusiveĬhunk 55381f9bf500ed80a204abd202f52ad3250b115e38af34a36371ab92726cf97c can't be foundĪnd the prune just aborts and does not complete. I am having an issue with the prune command. All issues Prune aborts with "chunk can't be found" error/warning ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |