# How to backup Discourse when The backup has failed?

**URL:** <https://meta.discourse.org/t/how-to-backup-discourse-when-the-backup-has-failed/159834>\
**Category:** Self-hosting\
**Created:** [August 4, 2020, 11:26pm UTC](https://meta.discourse.org/t/how-to-backup-discourse-when-the-backup-has-failed/159834 "2020-08-04T23:26:21Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![neounix](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/neounix/32/215617_2.png) [@neounix](https://meta.discourse.org/u/neounix)\
**Post date:** [August 5, 2020, 6:38am UTC](https://meta.discourse.org/t/how-to-backup-discourse-when-the-backup-has-failed/159834/7 "2020-08-05T06:38:23Z")

</div>

> [@pauln](#):
>
> It did fail as well. So our next option to do via command line?

Yes sir.

That should be fine.

Let us know how that goes or if you need more help. You will need to:

1. perform a manual dump of the postgres discourse db; and
2. create a manual archive of the uploads folder.

The instructions for creating the manual archives are OK in the reference above.

However, when I tested those directions just now, I could not write to the shared directory from inside the container, so I did this first (assuming your instance is `app`):

```plaintext
docker exec -it app bash
mkdir /shared/mybackups
chown postgres /shared/mybackups

```

and I changed all the paths to write to `/shared/mybackups` instead of `/shared` but you might not have that issue.

Looking forward to reading your progress soon.

---

_[View the full topic](https://meta.discourse.org/t/how-to-backup-discourse-when-the-backup-has-failed/159834)._
