# Automated backups not being triggered because cannot allocate memory

**URL:** <https://meta.discourse.org/t/automated-backups-not-being-triggered-because-cannot-allocate-memory/64265>\
**Category:** Product Support\
**Created:** [June 9, 2017, 8:59pm UTC](https://meta.discourse.org/t/automated-backups-not-being-triggered-because-cannot-allocate-memory/64265 "2017-06-09T20:59:33Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![JagWaugh](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jagwaugh/32/69335_2.png) [@JagWaugh](https://meta.discourse.org/u/JagWaugh)\
**Post date:** [June 10, 2017, 1:38pm UTC](https://meta.discourse.org/t/automated-backups-not-being-triggered-because-cannot-allocate-memory/64265/8 "2017-06-10T13:38:30Z")

</div>

> [@pfaffman](#):
>
> If you run discourse-setup it will tweak the memory settings

Interesting - I didn’t realise that running discourse-setup could be done on an install which was already up and running.

---

_[View the full topic](https://meta.discourse.org/t/automated-backups-not-being-triggered-because-cannot-allocate-memory/64265)._
