Recover volume in pending_destroy state - data still needed

[enesccinar]

Hi Fly team,

I’m hoping you can help me recover a volume that has gone into pending_destroy state.

Region: lax

Volume ID: vol_2gk9vwe9mz8v76wm
Volume name: pb_data
State: pending_destroy
Created: over 2 years ago

This volume contains our PocketBase production data. We noticed a new volume (vol_vwjy979nwq7mxjmr) was created automatically about 9 hours ago, but the old one with real data went into pending_destroy.

Snapshots from that old volume appear incomplete (only a few MB, while our real data.db is ~530 MB), so we’d like to reactivate the original volume or at least download/export its contents before it’s permanently deleted.

Could you please:

• Move this volume back to created state so I can attach it again, or

• Clone/export it to a new volume so I can access the data?

Thank you very much!

This data is critical, and it’s still within the 7-day pending_destroy window.

[lillian]

hey, this volume was actually migrated to a different host as part of regular operations, the new volume you noticed is a fork (clone) of the old one and contains all the same data.

I have recovered the original volume so you can attempt to recover the data; unfortunately, it is likely your app was misconfigured and was saving data to a non-permanent directory, in which case the data is unrecoverable.