# Creating a duplicate of production environment

**URL:** <https://meta.discourse.org/t/creating-a-duplicate-of-production-environment/61966>\
**Category:** Self-hosting\
**Created:** [2 mei 2017 om 15:38 UTC](https://meta.discourse.org/t/creating-a-duplicate-of-production-environment/61966 "2017-05-02T15:38:05Z")\
**Posts on this page:** 1\
**Showing post:** 19

<div class="post-metadata">

**Author:** ![mreach](https://avatars.discourse-cdn.com/v4/letter/m/9d8465/32.png) [@mreach](https://meta.discourse.org/u/mreach)\
**Post date:** [2 november 2019 om 22:28 UTC](https://meta.discourse.org/t/creating-a-duplicate-of-production-environment/61966/19 "2019-11-02T22:28:30Z")

</div>

This is a pretty important post, but could we also get some input and directions for processes that exclude a working backup system? I’m finding that the integrated backup doesn’t appear to have any way to function when you use an external database server. In my particular use case I’d like to take a production Discourse installation with a separated database server and then deploy it to a staging/test server where the database is INTEGRATED into the Dockerized setup.

I’ll post my findings once I get this working and what steps I took, but I figured this is a pretty important consideration for this topic.

---

_[View the full topic](https://meta.discourse.org/t/creating-a-duplicate-of-production-environment/61966)._
