# Recover pending\_destroy volumes from accidentally deleted parkwave-db app **URL:** \ **Category:** Questions / Help\ **Tags:** postgres, volumes\ **Created:** [August 19, 2026, 11:08am UTC](https://community.fly.io/t/recover-pending-destroy-volumes-from-accidentally-deleted-parkwave-db-app/28514 "2026-08-19T11:08:08Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![kkcom](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/kkcom/32/49764_2.png) [@kkcom](https://community.fly.io/u/kkcom)\ **Post date:** [August 19, 2026, 11:08am UTC](https://community.fly.io/t/recover-pending-destroy-volumes-from-accidentally-deleted-parkwave-db-app/28514/1 "2026-08-19T11:08:08Z")
I accidentally destroyed our production Legacy Postgres app `parkwave-db` approximately 15 hours ago. Organization: Personal Estimated deletion time: 2026-08-18 13:00 UTC Region: likely `sin` The Usage dashboard still shows three deleted `pg_data` volumes, each 10 GB, created on May 13, 2026 at 5:47 PM. The volumes may still be inside the 24-hour `pending_destroy` window. `fly volumes list --all -a parkwave-db` cannot retrieve them because the app no longer exists. Could a Fly engineer urgently preserve or recover these soft-deleted volumes, or provide their volume IDs before permanent purge? I understand Unmanaged Postgres itself is unsupported; this request is specifically for recovery of Fly App/Volume infrastructure resources. ---
**Author:** ![flyio-support](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/flyio-support/32/46245_2.png) [@flyio-support](https://community.fly.io/u/flyio-support)\ **Post date:** [August 19, 2026, 1:31pm UTC](https://community.fly.io/t/recover-pending-destroy-volumes-from-accidentally-deleted-parkwave-db-app/28514/3 "2026-08-19T13:31:15Z")
Hi there, I checked on my side and the app seems to exist with the three volumes in a “created” state. The _machines_ were destroyed, though, but the data should be there. You might be able to get it working with a `fly scale count 3` to get 3 new machines which will attach to the currently-orphaned volumes. Can you share the exact verbatim output you get with `fly volumes list --all -a parkwave-db`? ---
**Author:** ![kkcom](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/kkcom/32/49764_2.png) [@kkcom](https://community.fly.io/u/kkcom)\ **Post date:** [August 19, 2026, 2:57pm UTC](https://community.fly.io/t/recover-pending-destroy-volumes-from-accidentally-deleted-parkwave-db-app/28514/4 "2026-08-19T14:57:13Z")
Hi, thanks for checking. Here is the exact verbatim output I get: $ fly volumes list --all -a parkwave-db ID │ STATE │ NAME │ SIZE │ REGION │ ZONE │ ENCRYPTED │ ATTACHED VM │ CREATED AT vol\_vz85oeen3k72gezv │ created │ pg\_data │ 10GB │ sin │ f5d5 │ true │ │ 3 months ago vol\_rnz8xyyy6p2k1opr │ created │ pg\_data │ 10GB │ sin │ 7bcd │ true │ │ 3 months ago vol\_rnz8xyyj7kqny91r │ created │ pg\_data │ 10GB │ sin │ f1b9 │ true │ │ 3 months ago Warning: Metrics token unavailable: failed to run query($slug: String!) { organization(slug: $slug) { id internalNumericId slug rawSlug name type billable } }: context canceled All three volumes are in the “created” state and currently have no attached machines. Could you please confirm whether it is safe for me to run `fly scale count 3` now, and that it will attach the new machines to these existing volumes without reinitializing or overwriting their data? ---
**Author:** ![flyio-support](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/flyio-support/32/46245_2.png) [@flyio-support](https://community.fly.io/u/flyio-support)\ **Post date:** [August 19, 2026, 3:04pm UTC](https://community.fly.io/t/recover-pending-destroy-volumes-from-accidentally-deleted-parkwave-db-app/28514/5 "2026-08-19T15:04:12Z")
Hi, volume data won’t be overwritten. `fly scale count` will create new machines and attach them to existing volumes. ---
**Author:** ![kkcom](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/kkcom/32/49764_2.png) [@kkcom](https://community.fly.io/u/kkcom)\ **Post date:** [August 19, 2026, 3:07pm UTC](https://community.fly.io/t/recover-pending-destroy-volumes-from-accidentally-deleted-parkwave-db-app/28514/6 "2026-08-19T15:07:19Z")
```auto Thanks for confirming. All three volumes are now visible in the “created” state, and each volume still has snapshots available, including snapshots from approximately 20 hours ago. I’ll then verify that all three machines start correctly, determine the primary/replica status, and validate the database before reconnecting the backend. Thank you for your help recovering the app and volumes. ``` ---
**Author:** ![roadmr](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/roadmr/32/14140_2.png) [@roadmr](https://community.fly.io/u/roadmr)\ **Post date:** [August 19, 2026, 3:11pm UTC](https://community.fly.io/t/recover-pending-destroy-volumes-from-accidentally-deleted-parkwave-db-app/28514/7 "2026-08-19T15:11:12Z")
Great! To confirm, one of our engineers did undelete the app and the volumes, though apparently this wasn’t mentioned in this thread, this is why by the time I went to look, they were already undeleted. But it’s all good if you were able to bring it up! ---
**Author:** ![halfer](https://avatars.discourse-cdn.com/v4/letter/h/df705f/32.png) [@halfer](https://community.fly.io/u/halfer)\ **Post date:** [August 19, 2026, 3:52pm UTC](https://community.fly.io/t/recover-pending-destroy-volumes-from-accidentally-deleted-parkwave-db-app/28514/8 "2026-08-19T15:52:58Z")
Since no-one has yet mentioned it, is this a good time for you to configure an off-site PG data backup? ---
**Author:** ![kkcom](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/kkcom/32/49764_2.png) [@kkcom](https://community.fly.io/u/kkcom)\ **Post date:** [August 19, 2026, 4:36pm UTC](https://community.fly.io/t/recover-pending-destroy-volumes-from-accidentally-deleted-parkwave-db-app/28514/9 "2026-08-19T16:36:47Z")
Yes, definitely. I’ll set up the off-site PostgreSQL backup today. I’ll update the team once it’s configured and tested. ---
**Author:** ![halfer](https://avatars.discourse-cdn.com/v4/letter/h/df705f/32.png) [@halfer](https://community.fly.io/u/halfer)\ **Post date:** [August 19, 2026, 5:01pm UTC](https://community.fly.io/t/recover-pending-destroy-volumes-from-accidentally-deleted-parkwave-db-app/28514/10 "2026-08-19T17:01:42Z")
Super! You also have daily volume snapshots in Fly, and there’s no harm configuring those too, but I think off-site is essential. Perhaps an hourly push to a remote bucket. ---
**Author:** ![lubien](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/lubien/32/41919_2.png) [@lubien](https://community.fly.io/u/lubien)\ **Post date:** [August 19, 2026, 6:18pm UTC](https://community.fly.io/t/recover-pending-destroy-volumes-from-accidentally-deleted-parkwave-db-app/28514/12 "2026-08-19T18:18:57Z")
3 posts were split to a new topic: [failing sso login with aws system](https://community.fly.io/t/failing-sso-login-with-aws-system/28517) ---
**Author:** ![system](https://global.discourse-cdn.com/fly1/original/3X/6/e/6e8955d00cb218e186ebbe3a6ab06fefdce15290.svg) [@system](https://community.fly.io/u/system)\ **Post date:** [August 29, 2026, 7:13pm UTC](https://community.fly.io/t/recover-pending-destroy-volumes-from-accidentally-deleted-parkwave-db-app/28514/15 "2026-08-29T19:13:02Z")
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.