# Point in Time Recovery for Postgres Flex using Barman

**URL:** <https://community.fly.io/t/point-in-time-recovery-for-postgres-flex-using-barman/13185>\
**Category:** Fresh Produce\
**Tags:** postgres\
**Created:** [May 29, 2023, 12:03pm UTC](https://community.fly.io/t/point-in-time-recovery-for-postgres-flex-using-barman/13185 "2023-05-29T12:03:02Z")\
**Posts on this page:** 1\
**Showing post:** 22

<div class="post-metadata">

**Author:** ![stephentgrammer](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/stephentgrammer/32/18582_2.png) [@stephentgrammer](https://community.fly.io/u/stephentgrammer)\
**Post date:** [March 15, 2024, 5:22pm UTC](https://community.fly.io/t/point-in-time-recovery-for-postgres-flex-using-barman/13185/22 "2024-03-15T17:22:28Z")

</div>

@mayailurus after a couple of days of debugging and working with the very helpful folks at fly, we discovered that our db cluster was corrupted somehow. We [forked our database](https://community.fly.io/t/fork-yeah-new-volume-forking-feature-for-postgres/12390) and were consequently able to successfully SSH between machines and successfully perform a barman recovery! Case closed.

---

_[View the full topic](https://community.fly.io/t/point-in-time-recovery-for-postgres-flex-using-barman/13185)._