# Make "export db" optional when stopping a site **URL:** \ **Category:** Feature requests\ **Tags:** database, stop-site\ **Created:** [February 15, 2018, 11:21am UTC](https://community.localwp.com/t/make-export-db-optional-when-stopping-a-site/5260 "2018-02-15T11:21:12Z")\ **Posts on this page:** 15\ **Page:** 1
**Author:** ![robsat91](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/robsat91/32/4849_2.png) [@robsat91](https://community.localwp.com/u/robsat91)\ **Post date:** [February 15, 2018, 11:21am UTC](https://community.localwp.com/t/make-export-db-optional-when-stopping-a-site/5260/1 "2018-02-15T11:21:12Z")
Hello! I love Local, keep up the good work! 🙂 I’ve noticed that each time i stop a site then Local does a backup. This is initially a good thing, but it should really be an optional feature. I have a lot of sites in my Local setup, and I start and stop them often since i’m working in the support-branch of my company. When stopping/restarting a container the backup makes the process really slow, and the disk gets clogged up with huge sql-files. If a site would fail for some reason then I just set it up again with fresh data from production environment. So if the site environment should fail loosing data is not an issue. Is some of these alternatives possible to realize in the future? - compresse the SQL-files (.zip/.tar.gz) - make the backup optional I understand that this is not an issue for the average Joe, but hopefully making this feature optional is not too much work. This also makes Local more future proof as this feature help the keep the disk usage lower for those who wants. Best regards, Robert Sæther Dekode Interaktiv AS ---
**Author:** ![simonb](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/simonb/32/4864_2.png) [@simonb](https://community.localwp.com/u/simonb)\ **Post date:** [February 18, 2018, 4:32pm UTC](https://community.localwp.com/t/make-export-db-optional-when-stopping-a-site/5260/2 "2018-02-18T16:32:57Z")
I’ve got a couple of sites with huge databases, Local can take a couple of minutes or more to stop them due to the time the backup process takes, so this would be a great feature to have. ---
**Author:** ![turtlepod](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/turtlepod/32/5541_2.png) [@turtlepod](https://community.localwp.com/u/turtlepod)\ **Post date:** [March 9, 2018, 6:35pm UTC](https://community.localwp.com/t/make-export-db-optional-when-stopping-a-site/5260/3 "2018-03-09T18:35:43Z")
Is there a way to disable “backup” when stoping a site? I use Local in a relatively big site, and backing up can take a long time. It would be great if there’s a way to disable backup when stoping/restart. If there’s no way to do this, maybe feature request? Thank you. ---
**Author:** ![clay](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/clay/32/8248_2.png) [@clay](https://community.localwp.com/u/clay)\ **Post date:** [March 9, 2018, 10:50pm UTC](https://community.localwp.com/t/make-export-db-optional-when-stopping-a-site/5260/4 "2018-03-09T22:50:31Z")
@turtlepod, I moved your post into this feature request. Make sure you vote it up! 🙂 ---
**Author:** ![turtlepod](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/turtlepod/32/5541_2.png) [@turtlepod](https://community.localwp.com/u/turtlepod)\ **Post date:** [March 10, 2018, 1:13am UTC](https://community.localwp.com/t/make-export-db-optional-when-stopping-a-site/5260/5 "2018-03-10T01:13:58Z")
thanks @clay ---
**Author:** ![robsat91](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/robsat91/32/4849_2.png) [@robsat91](https://community.localwp.com/u/robsat91)\ **Post date:** [March 10, 2018, 8:56am UTC](https://community.localwp.com/t/make-export-db-optional-when-stopping-a-site/5260/6 "2018-03-10T08:56:14Z")
Thanks, much appreciated! ---
**Author:** ![Mamaduka](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/mamaduka/32/92_2.png) [@Mamaduka](https://community.localwp.com/u/Mamaduka)\ **Post date:** [January 29, 2019, 2:51pm UTC](https://community.localwp.com/t/make-export-db-optional-when-stopping-a-site/5260/7 "2019-01-29T14:51:14Z")
This feature would be really nice to have. ---
**Author:** ![robsat91](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/robsat91/32/4849_2.png) [@robsat91](https://community.localwp.com/u/robsat91)\ **Post date:** [March 12, 2019, 7:31pm UTC](https://community.localwp.com/t/make-export-db-optional-when-stopping-a-site/5260/8 "2019-03-12T19:31:41Z")
Bumping this up again. These SQL-files take up huge space on my disk, and they also take a while to dump when I’m trying to stop a site. Nice feature for someone, a time consuming issue for others. Would be nice to make this feature optional 🙂 ---
**Author:** ![robsat91](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/robsat91/32/4849_2.png) [@robsat91](https://community.localwp.com/u/robsat91)\ **Post date:** [April 15, 2019, 1:30pm UTC](https://community.localwp.com/t/make-export-db-optional-when-stopping-a-site/5260/9 "2019-04-15T13:30:48Z")
Any update on this topic @clay? 🙂 ---
**Author:** ![Mamaduka](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/mamaduka/32/92_2.png) [@Mamaduka](https://community.localwp.com/u/Mamaduka)\ **Post date:** [June 27, 2019, 9:39am UTC](https://community.localwp.com/t/make-export-db-optional-when-stopping-a-site/5260/10 "2019-06-27T09:39:37Z")
Any update on this request? ---
**Author:** ![kingkool68](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/kingkool68/32/5054_2.png) [@kingkool68](https://community.localwp.com/u/kingkool68)\ **Post date:** [February 5, 2020, 10:21pm UTC](https://community.localwp.com/t/make-export-db-optional-when-stopping-a-site/5260/11 "2020-02-05T22:21:51Z")
I just Command + Q the Local by Flywheel app and it shuts down without doing a database dump. Haven’t run into any problems doing it that way. ---
**Author:** ![Mamaduka](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/mamaduka/32/92_2.png) [@Mamaduka](https://community.localwp.com/u/Mamaduka)\ **Post date:** [March 10, 2020, 6:39am UTC](https://community.localwp.com/t/make-export-db-optional-when-stopping-a-site/5260/12 "2020-03-10T06:39:36Z")
Is something that can be done via add-on? If anyone can point me in the right direction happy to write one. ---
**Author:** ![ben.turner](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/ben.turner/32/5366_2.png) [@ben.turner](https://community.localwp.com/u/ben.turner)\ **Post date:** [September 20, 2021, 6:16pm UTC](https://community.localwp.com/t/make-export-db-optional-when-stopping-a-site/5260/13 "2021-09-20T18:16:19Z")
I’m trying to clean up and clarify old feature requests. In this case, I renamed the topic to make it more specific to configuring what things Local does with the database when a site is stopped. Is preventing the DB from being exported the only thing you want configured when stopping a site? > [@Mamaduka](#): > > Is something that can be done via add-on? I don’t think that the necessary hooks are in place to be able to control this via a plugin. ---
**Author:** ![luke.iccir](https://avatars.discourse-cdn.com/v4/letter/l/22d042/32.png) [@luke.iccir](https://community.localwp.com/u/luke.iccir)\ **Post date:** [September 30, 2026, 8:54am UTC](https://community.localwp.com/t/make-export-db-optional-when-stopping-a-site/5260/14 "2026-09-30T08:54:14Z")
Are there any updates on this one? For me, having a toggle to enable/disable auto-backup on stop on a per-site basis would be enough. I’m currently working on a migration of a 70GB database so having the ability to skip the backup is crucial. ---
**Author:** ![Nick-B](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/nick-b/32/16140_2.png) [@Nick-B](https://community.localwp.com/u/Nick-B)\ **Post date:** [September 30, 2026, 2:31pm UTC](https://community.localwp.com/t/make-export-db-optional-when-stopping-a-site/5260/16 "2026-09-30T14:31:23Z")
No updates on this @luke.iccir but I’ve raised it back up with the team for discussion. Thanks for reaching out!