# 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:** 24

<div class="post-metadata">

**Author:** ![stephen1](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/stephen1/32/13882_2.png) [@stephen1](https://community.fly.io/u/stephen1)\
**Post date:** [April 10, 2024, 7:33pm UTC](https://community.fly.io/t/point-in-time-recovery-for-postgres-flex-using-barman/13185/24 "2024-04-10T19:33:16Z")

</div>

> This means for a 30 day retention window your barman volume needs to be over 30× the size of your postgres volumes.

I only think this would be true if you were at capacity on your postgres volume. Although the barman volume needs to be at least as large as your postgres volume, each backup only seems to use the storage necessary for the data being backed up (which could be quite small). That’s what it seems to do when I do a barman backup but maybe I’m missing something though!

---

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