# Better auto-backup options

**URL:** <https://meta.discourse.org/t/better-auto-backup-options/33351>\
**Category:** Feature\
**Tags:** backups, s3\
**Created:** [16 Septiembre, 2015 13:20 UTC](https://meta.discourse.org/t/better-auto-backup-options/33351 "2015-09-16T13:20:43Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![ky\_metro](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ky_metro/32/42807_2.png) [@ky\_metro](https://meta.discourse.org/u/ky_metro)\
**Post date:** [16 Septiembre, 2015 13:20 UTC](https://meta.discourse.org/t/better-auto-backup-options/33351/1 "2015-09-16T13:20:43Z")

</div>

We could use a few more options for automatic backups. Digital Ocean offers pretty limited disk space, whereas S3 is infinite. Currently they are synced together, meaning S3 is limited to available local space. On my site, that means two daily backups complete, then the process stalls.

Here’s some ideas:

- Option to backup database only (no files). This option is available already for manual backups. It saves a lot of space for file-heavy sites, and allows more backups to be stored locally.

- Better scheduler. With two backup options, you will want the ability to do both at different times (ie daily database backups plus weekly full backup).

- Option to manage S3 storage separate from Discourse. Again, with limited local disk space, I’d like the option to keep one daily backup on local disk but infinite backups on S3.

- If there’s not enough local disk space left, delete the oldest backup before starting a new one. This would prevent a full disk from stalling your backups, assuming they are similar in size.

- Notification if auto-backup failed to run. Right now it fails silently, and I have to remember to check on it.

---

_[View the full topic](https://meta.discourse.org/t/better-auto-backup-options/33351)._