# Has anyone lost data with Kopia?

**URL:** <https://kopia.discourse.group/t/has-anyone-lost-data-with-kopia/2043>\
**Category:** General Topics\
**Created:** [May 16, 2023, 9:40pm UTC](https://kopia.discourse.group/t/has-anyone-lost-data-with-kopia/2043 "2023-05-16T21:40:52Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![jit010101](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/jit010101/32/785_2.png) [@jit010101](https://kopia.discourse.group/u/jit010101)\
**Post date:** [September 20, 2023, 7:03pm UTC](https://kopia.discourse.group/t/has-anyone-lost-data-with-kopia/2043/2 "2023-09-20T19:03:42Z")

</div>

> [@Kopia repository 'corrupted itself' (unable to add to XXX index blob cache: context canceled)](https://kopia.discourse.group/t/kopia-repository-corrupted-itself-unable-to-add-to-xxx-index-blob-cache-context-canceled/1766):
>
> I had a working Kopia repo with around 100TB of data - everything was going well, it has not been touched for two weeks or so. I kicked of a small incremental backup today, which completed successfully: \* 0 hashing, 338337 hashed (878.7 GB), 28078694 cached (94.8 TB), uploaded 876.2 GB, estimated 22 TB (435.2%) 0s left Created snapshot with root k3ad2929159e95246105260ef08b97a3d818b4fc02c580e8816fefe8413946756 and ID 3bee2c042f4de4cb7088f9ef616462e8 in 36m59s However, after a while (maybe wh…

---

_[View the full topic](https://kopia.discourse.group/t/has-anyone-lost-data-with-kopia/2043)._
