# SQLite file in Volume lost data on deploy

**URL:** <https://community.fly.io/t/sqlite-file-in-volume-lost-data-on-deploy/6126>\
**Category:** General\
**Created:** [July 23, 2022, 4:10pm UTC](https://community.fly.io/t/sqlite-file-in-volume-lost-data-on-deploy/6126 "2022-07-23T16:10:53Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![greg](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/greg/32/2119_2.png) [@greg](https://community.fly.io/u/greg)\
**Post date:** [July 23, 2022, 10:43pm UTC](https://community.fly.io/t/sqlite-file-in-volume-lost-data-on-deploy/6126/4 "2022-07-23T22:43:18Z")

</div>

Ah. If so, that would explain it. The volume is independent of the app and that would persist across deploys.

As you’ve seen, Fly also take snapshots of volumes and they can manually restore them (see thread below). But if your database was not _on_ that volume, I guess that won’t be much help here ☹

> [@Volume sometimes resets on deploy](https://community.fly.io/t/volume-sometimes-resets-on-deploy/4244/4):
>
> Ok, I looked at your app and one of the volumes you previously deleted it still hanging out. So what’s happening is that your app is booting on two different volumes. Does the volume it’s running on have the data you need? Or is it the other one? We can restore that other one pretty easily. There’s no automated way to restore snapshots yet (I don’t think!). It’s built but not shipped.

---

_[View the full topic](https://community.fly.io/t/sqlite-file-in-volume-lost-data-on-deploy/6126)._