# Recommended backup process for very large forum?

**URL:** <https://meta.discourse.org/t/recommended-backup-process-for-very-large-forum/65999>\
**Category:** Support\
**Created:** [11. Juli 2017 um 14:16 UTC](https://meta.discourse.org/t/recommended-backup-process-for-very-large-forum/65999 "2017-07-11T14:16:56Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![mpalmer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mpalmer/32/45740_2.png) [@mpalmer](https://meta.discourse.org/u/mpalmer)\
**Post date:** [11. Juli 2017 um 23:04 UTC](https://meta.discourse.org/t/recommended-backup-process-for-very-large-forum/65999/5 "2017-07-11T23:04:15Z")

</div>

> [@Sander78](#):
>
> Would it be possible for Discourse to create delta backups in the near future?

I’d consider it _extremely_ unlikely. Taking a diff of a relational database is far from trivial, and the gains are minimal. If you’re running a large enough site to make app-level “delta backups” worthwhile, you’re probably going to be switching off Discourse’ built-in backups anyway, and using `pg_basebackup`+WAL archiving to hit your RPO targets (which, as a bonus, gives you point-in-time restoration capability).

---

_[View the full topic](https://meta.discourse.org/t/recommended-backup-process-for-very-large-forum/65999)._