# Multiple backup schedules

**URL:** <https://meta.discourse.org/t/multiple-backup-schedules/223312>\
**Category:** Feature\
**Created:** [April 5, 2022, 8:36am UTC](https://meta.discourse.org/t/multiple-backup-schedules/223312 "2022-04-05T08:36:27Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![RGJ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rgj/32/523185_2.png) [@RGJ](https://meta.discourse.org/u/RGJ)\
**Post date:** [April 12, 2022, 3:03pm UTC](https://meta.discourse.org/t/multiple-backup-schedules/223312/7 "2022-04-12T15:03:45Z")

</div>

> [@Jagster](#):
>
> Database itself is totally different ball game. It should be done at least every 15 minutes if there is more traffic.
> 
> The question is really easy: how much content you can loose.

If the maximum data loss you can afford is this small then you might consider using a Postgres replication solution instead of taking backups so frequently.

---

_[View the full topic](https://meta.discourse.org/t/multiple-backup-schedules/223312)._
