# Hourly backup, only if something has changed

**URL:** <https://meta.discourse.org/t/hourly-backup-only-if-something-has-changed/27274>\
**Category:** Feature\
**Tags:** backups\
**Created:** [6 april 2015 om 21:57 UTC](https://meta.discourse.org/t/hourly-backup-only-if-something-has-changed/27274 "2015-04-06T21:57:56Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![frederic](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/frederic/32/38177_2.png) [@frederic](https://meta.discourse.org/u/frederic)\
**Post date:** [7 april 2015 om 08:49 UTC](https://meta.discourse.org/t/hourly-backup-only-if-something-has-changed/27274/5 "2015-04-07T08:49:50Z")

</div>

Hello

> [@sam](#):
>
> Technically doable in a plugin but sounds VERY odd. What you would really like is some sort of delta, say every 10 minutes. That is much more technically tricky but ultimately way more useful.

As a user, I need something as simple as what is actually implemented and works really great : if something is wrong (hoster fails), I go to [aws.amazon.com](http://aws.amazon.com), download the latest backup, launch a new VM instance, install discourse via docker in a snap and restore the backup.

> [@riking](#):
>
> Sounds like streaming replication is what we want here, to me.

Probably, but I need a simple restore process. 😄

> [@Mittineague](#):
>
> For a typical forum every 10 minutes seems a bit extreme, it’s not financial transactions happening.
> 
> Surely there must be a more reasonable balance between risk of data loss \<-\> resource use

In fact, I analyzed the risks (very low) and the cost :

- Backup process is probably CPU intensive for the VM, but if the system is as smart as “do backup every hour only if something changed”, that will be a good balance to me. “Every hour” could be adapted to each case, for example : “every 3 hours” for a larger instance

- S3 or alternatives like Hubic are very cheap, and their use will be optimized by the “only if” option

- Two separate archives (one for the uploaded files, one other for the rest) would definitely optimize the process, but restore should be more tricky.

To be simple and because my instance is very small (60 Mo), I think the only thing I need to start on a cheaper VPS, is to be able to lower the nightly archive frequency to every one or two hours instead of every 24 hours.

Do you know if it is possible to add this hack in the app.yml ?

Many thanks !

---

_[View the full topic](https://meta.discourse.org/t/hourly-backup-only-if-something-has-changed/27274)._
