# Support for automatic backup encryption (GPG?)

**URL:** <https://meta.discourse.org/t/support-for-automatic-backup-encryption-gpg/25124>\
**Category:** Feature\
**Tags:** backups\
**Created:** [February 11, 2015, 11:12am UTC](https://meta.discourse.org/t/support-for-automatic-backup-encryption-gpg/25124 "2015-02-11T11:12:52Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![riking](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/riking/32/170938_2.png) [@riking](https://meta.discourse.org/u/riking)\
**Post date:** [February 12, 2015, 2:51am UTC](https://meta.discourse.org/t/support-for-automatic-backup-encryption-gpg/25124/3 "2015-02-12T02:51:09Z")

</div>

Word of advice: you (in particular) will likely want to rename, let’s say one backup a month, to a name that Discourse won’t auto-delete when it reaches the maximum daily backups limit, and mirror that selected one elsewhere.

Just breaking the date format should suffice to avoid the auto-deletion (e.g. 2015-02-11 into 2015\_Feb or something like that).

You’ll also be able to be a bit more lax in where you put the backups, because they’re encrypted and the private key is offline.

(Further explaining that: Backups contain all the private messages and drafts stored on the server! Which is why there’s a standard admonishment to not let non-admins get backups.)

---

_[View the full topic](https://meta.discourse.org/t/support-for-automatic-backup-encryption-gpg/25124)._