Hi… You should be able to resolve this in a self-service way using volume forking:
By default, we place the new volume on a separate physical host in the same region.
For larger volumes, it will spend some time in a “hydrating” state, where the data is accessible but with slower/worse performance. It will catch up on its own eventually, though.
Hope this helps!
Aside: If you have a Fly Support plan, then it’s generally best to contact them directly, rather than here in the community forum.