Does KopiaUI not verify snapshots?

[dimejo]

@ekutner

There is some very valuable information here but is there any decent documentation for the maintenance commands? In particular, what do each of snapshot verify, content verify and maintenance run do?

Best method to ensure valid snapshots: snapshot verify vs snapshot fix invalid-files

There are many verification methods, depending on what you need. In the order of lowest- to highest-level: kopia content verify - will ensure that content manager index structures are correct and that every index entry is backed by an existing file kopia content verify --download-percent=10 - same as above, but will download 10% of random contents and ensure they can be decrypted properly kopia snapshot verify - will ensure that directory structures in the repository are consistent by …

In short:

• kopia content verify does the same as kopia snapshot verify, but doesn’t detect missing blobs.
• Running kopia snapshot verify regularly is not necessary, because it is part of a full maintenance run.
• It is not recommend to run kopia snapshot fix automatically, only when a problem is detected.
• Running kopia snapshot verify --verify-files-percent=X daily is recommended and the best way to make sure your repository is in good shape.

@ekutner

However, I don’t understand how it could happen, because I’m backing up to a directly attached internal hard drive, which doesn’t report any errors.

It’s always hard to tell why these errors happen, but I would reommend running an extended SMART test and a memtest.

@ekutner

I tried running “snapshot verify --verify-files-percent=10” and it didn’t report any errors, so I’m trying again on 100% but either way, since I I don’t know what it actually does, I don’t know what to make of these findings or how to fix them.

kopia snapshot fix invalid-files has reliably fixes errors for me in the past. Maybe make a copy of your repository if you don’t feel comfortable using --commit.

@ekutner

As a side note it’s also worth mentioning that this verification process is unreasonably slow. It has been running for more than 2 hours now and only processed about 6% of the objects.

You didn’t mention the size of the repository or the hardware you are running on, so it is hard to tell what unreasonably slow means. The command generally is CPU-bound, because it has to decrypt, decompress and hash every single blob. What does your CPU usage look like?