# Clarify QDB Upgrades and the hidden .questdb directory

**URL:** <https://community.questdb.com/t/clarify-qdb-upgrades-and-the-hidden-questdb-directory/896>\
**Category:** Community\
**Tags:** question\
**Created:** [July 24, 2025, 9:28am UTC](https://community.questdb.com/t/clarify-qdb-upgrades-and-the-hidden-questdb-directory/896 "2025-07-24T09:28:44Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![paris](https://avatars.discourse-cdn.com/v4/letter/p/b9e5f3/32.png) [@paris](https://community.questdb.com/u/paris)\
**Post date:** [July 24, 2025, 9:28am UTC](https://community.questdb.com/t/clarify-qdb-upgrades-and-the-hidden-questdb-directory/896/1 "2025-07-24T09:28:44Z")

</div>

I’m upgrading QuestDB for the first time (Linux rt x86).

Please clarify how to treat the hidden directory .questdb during an upgrade, which I believe stores all my table data. Can I leave .questdb as is from minor version upgrades, like 9.0.0 to 9.0.1? How about from 8.2 to 8.3 for example?

How about major versions? Do I have to re-create all my database records during a major version upgrade? Or can I just use .questdb?

Does the `_restore` file come into play during a migration of a major version upgrade like 8.0 to 9.0? Will this restore signal help in recreating my data during a version update?

Please explain all things upgrade, I don’t see anything in the docs related to this, except a brief mention for Docker, but I’m not using Docker. Also, please clarify .questdb and when it becomes obsolete, and tips for recreating it in case such obsolescence exists.

Thanks! And nice job with QDB!  
Paris

---

<div class="post-metadata">

**Author:** ![nwoolmer](https://yyz2.discourse-cdn.com/flex004/user_avatar/community.questdb.com/nwoolmer/32/24_2.png) [@nwoolmer](https://community.questdb.com/u/nwoolmer)\
**Post date:** [July 24, 2025, 9:31am UTC](https://community.questdb.com/t/clarify-qdb-upgrades-and-the-hidden-questdb-directory/896/2 "2025-07-24T09:31:21Z")

</div>

Stop the database, swap out the `/bin` and `/lib` folders with new ones, start the database.

There is no need to touch anything else, besides checking release-notes for any relevant breaking changes.
