Scenario: I have a filesystem-based Kopia repository with a snapshot of an external HDD on it. I’ve recently moved the external HDD partition and I want to use Kopia to ensure the move happened without introducing corruption.
I’ve reviewed Data corruption checking - Flag clarification, and I first attempted to use
kopia snapshot create /app/backup --force-hash 100, but it seems to be uploading fresh data to the repository, not just rehashing and recognizing that the blobs already exist in the repo. I also tried
kopia snapshot verify --verify-files-percent 100, but this seems to take forever (>10 hours) to list the blobs on a 2TiB repo and then gives an estimated time remaining of 1,500 hours.
I thought the forced hash on snapshot create was going to be exactly what I needed, allowing me to verify that the snapshot root was unchanged from the before-the-move snapshot and use
snapshot diff to investigate any differences.
Any guidance is very much appreciated.