# Is there a return code of kopia snapshot verify if verification fails?

**URL:** <https://kopia.discourse.group/t/is-there-a-return-code-of-kopia-snapshot-verify-if-verification-fails/3260>\
**Category:** Support\
**Created:** [September 12, 2024, 11:55am UTC](https://kopia.discourse.group/t/is-there-a-return-code-of-kopia-snapshot-verify-if-verification-fails/3260 "2024-09-12T11:55:35Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![peter](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/peter/32/441_2.png) [@peter](https://kopia.discourse.group/u/peter)\
**Post date:** [September 12, 2024, 11:55am UTC](https://kopia.discourse.group/t/is-there-a-return-code-of-kopia-snapshot-verify-if-verification-fails/3260/1 "2024-09-12T11:55:35Z")

</div>

I want to run verification as background process and thought about doing something like

`kopia snapshot verify --verify-files-percent=100 || notify-send --urgency=critical --icon=dialog-error --category=error --expire-time=0 "Backup Verification Failed" "An error was reported when verifying kopia backup"`

I found [`kopia snapshot verify` exits with status code 0 even when it didn't finish successfully · Issue #3605 · kopia/kopia · GitHub](https://github.com/kopia/kopia/issues/3605) which could imply that normally there should be an error code.

---

<div class="post-metadata">

**Author:** ![Jesus\_Lopez](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/jesus_lopez/32/803_2.png) [@Jesus\_Lopez](https://kopia.discourse.group/u/Jesus_Lopez)\
**Post date:** [September 16, 2024, 12:00pm UTC](https://kopia.discourse.group/t/is-there-a-return-code-of-kopia-snapshot-verify-if-verification-fails/3260/2 "2024-09-16T12:00:46Z")

</div>

Just bumping this, I also use verify, in cron to check the health of the repo.

---

<div class="post-metadata">

**Author:** ![randombyte-developer](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/randombyte-developer/32/696_2.png) [@randombyte-developer](https://kopia.discourse.group/u/randombyte-developer)\
**Post date:** [September 25, 2024, 5:40pm UTC](https://kopia.discourse.group/t/is-there-a-return-code-of-kopia-snapshot-verify-if-verification-fails/3260/3 "2024-09-25T17:40:23Z")

</div>

I am checking the return status like this [my-kopia-docker/scheduler/run.sh at master · randombyte-developer/my-kopia-docker · GitHub](https://github.com/randombyte-developer/my-kopia-docker/blob/master/scheduler/run.sh#L19) on a daily run. I am checking it through `docker exec` but I guess it should be the same when executing it on the same machine.

I can confirm that it fails when there is a verification error. I have simulated this. Also it will fail when the container’s host ran out of storage space (due to large cache sizes of kopia and multiple instances). It will also fail when unplugging my local backup drive. And it will also fail when the remote backup service it unreachable.

---

<div class="post-metadata">

**Author:** ![97b4958b055b](https://avatars.discourse-cdn.com/v4/letter/9/47e85d/32.png) [@97b4958b055b](https://kopia.discourse.group/u/97b4958b055b)\
**Post date:** [March 21, 2025, 8:41pm UTC](https://kopia.discourse.group/t/is-there-a-return-code-of-kopia-snapshot-verify-if-verification-fails/3260/4 "2025-03-21T20:41:31Z")

</div>

> [@peter](#):
>
> I found [`kopia snapshot verify` exits with status code 0 even when it didn’t finish successfully · Issue #3605 · kopia/kopia · GitHub](https://github.com/kopia/kopia/issues/3605) which could imply that normally there should be an error code.

[#3605](https://github.com/kopia/kopia/issues/3605) was opened Q1 2024. It is now the week heading into Q2 2025. There have been [**seven** (7) releases](https://github.com/kopia/kopia/releases/tag/v0.16.1) since [it was acknowledged](https://github.com/kopia/kopia/issues/3605#event-11692084869).

What is this project?

---

<div class="post-metadata">

**Author:** ![IcePic](https://avatars.discourse-cdn.com/v4/letter/i/74df32/32.png) [@IcePic](https://kopia.discourse.group/u/IcePic)\
**Post date:** [April 4, 2025, 12:15pm UTC](https://kopia.discourse.group/t/is-there-a-return-code-of-kopia-snapshot-verify-if-verification-fails/3260/5 "2025-04-04T12:15:54Z")

</div>

> [@97b4958b055b](#):
>
> What is this project?

An opportunity!

Or, you could just ask for all your money back, if not satisfied with the current status.

---

<div class="post-metadata">

**Author:** ![97b4958b055b](https://avatars.discourse-cdn.com/v4/letter/9/47e85d/32.png) [@97b4958b055b](https://kopia.discourse.group/u/97b4958b055b)\
**Post date:** [April 5, 2025, 2:27am UTC](https://kopia.discourse.group/t/is-there-a-return-code-of-kopia-snapshot-verify-if-verification-fails/3260/6 "2025-04-05T02:27:02Z")

</div>

It’s still a staggeringly steep price to pay given what’s expected to be put at stake.

> [@Disk full - Snapshot delete not possible !?](https://kopia.discourse.group/t/disk-full-snapshot-delete-not-possible/1759):
>
> Hi there, the following happened to me: i made a backup to an external usb hard disk. The usb disk filled up and the backup was interrupted in kopia. Now i wanted to delete this snapshot. but i can’t, because kopia tells me, that there is no space left on the disk when i try to delete. And now?
