# Should I re-setup a very long living (always updated) installation? **URL:** \ **Category:** ℹ️ Support\ **Tags:** desktop-client, windows, nc29, aio\ **Created:** [October 4, 2024, 12:22pm UTC](https://help.nextcloud.com/t/should-i-re-setup-a-very-long-living-always-updated-installation/206008 "2024-10-04T12:22:23Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![wwe](https://help.nextcloud.com/user_avatar/help.nextcloud.com/wwe/32/72963_2.png) [@wwe](https://help.nextcloud.com/u/wwe)\ **Post date:** [October 8, 2024, 8:35pm UTC](https://help.nextcloud.com/t/should-i-re-setup-a-very-long-living-always-updated-installation/206008/3 "2024-10-08T20:35:00Z")
In general I don’t feel “complete makeover” is a good choice. It might be a good solution if you somehow screw up your installation but you should know what you do - e.g. starting with empty DB will likely reduce your oc\_filecache but is it worth loosing all the versions, file\_trash, shares etc? I would look at the table **first** - often such extreme sizes result from external storage… maybe “cross-shared” mounts etc… you can start with looking at this table with simple `select * from oc_storages` and checking if there are obsolete storages… you can add count and sum clauses to understand where the most items come from maybe [Oc\_filecache.ibd very large](https://help.nextcloud.com/t/oc-filecache-ibd-very-large/107632) helps… Once you finished clean-up (and hopefully report successful steps here) you can look at [Nextcloud docker-compose setup with notify\_push (2024)](https://help.nextcloud.com/t/nextcloud-docker-compose-setup-with-notify-push-2024/186721) and [Nextcloud docker compose setup with Caddy (2024)](https://help.nextcloud.com/t/nextcloud-docker-compose-setup-with-caddy-2024/204846) to improve your installation with modern Docker technics --- _[View the full topic](https://help.nextcloud.com/t/should-i-re-setup-a-very-long-living-always-updated-installation/206008)._