I’ve used Kopia for many months. I’m on Windows 11. I have 3 repositories, they are all local repositories.
Now, one of them can’t be opened by Kopia UI anymore - instead the other two are ok.
So, I’ve tried to open it from a DOS shell, by the command:
kopia repository connect
and on the second attempt, it opened it.
Being connected, I tried the command:
kopia snapshot list
and it failed, with the messages:
Found too many index blobs (2061), this may result in degraded performance.
Please ensure periodic repository maintenance is enabled or run 'kopia maintenance'.
error listing all snapshot manifests: unable to find snapshot manifests: unable to load manifest contents: error loading manifest content: invalid checksum
at q1e6d1134f4918fec8007c4f12873a9c7-se21172b0e857259b13d offset 32 length 580/580: decrypt: unable to decrypt content: cipher: message authentication failed
I think that these are two different messages, one related to manintenance, and another one, uncorrelated to the first, about a missing (or a corructed?) file…
Can anyone help me?
I need to be able to use Kopia UI, because I don’t have technical skill enough to use the command-line mode… (anyway, now the command-line doesn’t work even…)
Well… invalid checksum can’t be good. You could start with a
kopia snapshot verify
and see, what its output is. Then you should search the mentioned file in your repo and inspect it. Does it have an actual size, or does it have a weird timestamp? I think that this file might be the manifest for a single snapshot, so maybe removing it will only nuke the correspondig snapshot, but I am not sure about that. I any event, I’d save this file and not just delete it from the repo.
Its just a shot in the dark, but as long as you keep the file around, you could try removing/renaming it and try to run snapshot verify again.
please consider the ‘\’ characters… so a directory named q1e (first 3 chars of my string), inside it has a subdirectory 6d1 (second 3 chars of my string), which inside has a file, the name of which is the rest of the string.
By the way, the file I tried to remove wasn’t “strange”, in the sense that it has size > 0, and two valid timestamps (created on/last modified on).
Isn’t there a way to manually remove all the files of last snaphots, keeping only the older snapshots? I know that e.g. on 01.02.2026, and before this date, the snaphots were successful… So removing the newest part, shouldn’t I get back the access to my repository?
Ok, you could remove both files and then perform a kopia snapshot verify. Hower, I’d rather rename those instead to keep them “nearby”.
Then you could run a kopia snapshot fix invalid-files and see where that takes you. This will not remove any files, but it should give you a glimpse on what Kopia seem to consider as invalid.
Afterwards you could go ahead an run kopia snapshot fix invalid-files –commit. Then run a kopia snapshot verify.