# Restoring Discourse 1.9 backup onto v2.3.0.beta9 +184

**URL:** https://meta.discourse.org/t/restoring-discourse-1-9-backup-onto-v2-3-0-beta9-184/117001
**Category:** Support
**Created:** [5월 6, 2019, 8:57오후 UTC](https://meta.discourse.org/t/restoring-discourse-1-9-backup-onto-v2-3-0-beta9-184/117001 "2019-05-06T20:57:54Z")
**Posts on this page:** 10
**Page:** 1

<div class="post-metadata">

### Author: ![oluies](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/oluies/32/120194_2.png) [@oluies](https://meta.discourse.org/u/oluies)
#### Post date: [5월 6, 2019, 8:57오후 UTC](https://meta.discourse.org/t/restoring-discourse-1-9-backup-onto-v2-3-0-beta9-184/117001/1 "2019-05-06T20:57:54Z")

</div>

![image](https://global.discourse-cdn.com/meta/original/3X/0/8/08db17a1534ebf1c53b2ac7deabe268bab2e6361.png)

> ERROR: cannot drop table users column email because other objects depend on it  
> DETAIL: trigger users\_email\_readonly on table users depends on table users column email  
> HINT: Use DROP … CASCADE to drop the dependent objects too.

---

<div class="post-metadata">

### Author: ![oluies](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/oluies/32/120194_2.png) [@oluies](https://meta.discourse.org/u/oluies)
#### Post date: [5월 7, 2019, 5:25오전 UTC](https://meta.discourse.org/t/restoring-discourse-1-9-backup-onto-v2-3-0-beta9-184/117001/2 "2019-05-07T05:25:59Z")

</div>

So the docker install [discourse/docs/INSTALL-cloud.md at main · discourse/discourse · GitHub](https://github.com/discourse/discourse/blob/master/docs/INSTALL-cloud.md) install the LATEST… how to select a stable version?

---

<div class="post-metadata">

### Author: ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [5월 7, 2019, 5:30오전 UTC](https://meta.discourse.org/t/restoring-discourse-1-9-backup-onto-v2-3-0-beta9-184/117001/3 "2019-05-07T05:30:01Z")

</div>

Downgrading isn’t supported, you can’t roll back to beta or stable until they pass the current tests-passed. You can use the commit ID as per [this topic](https://meta.discourse.org/t/change-tracking-branch-for-your-discourse-instance/17014), but it’s very unlikely a routine upgrade is the cause - Discourse _isn’t_ prone to spontaneous combustion.

Do you have sufficient free space on the server? Have you disabled all plugins and re-tried?

---

<div class="post-metadata">

### Author: ![michaeld](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/michaeld/32/1594_2.png) [@michaeld](https://meta.discourse.org/u/michaeld)
#### Post date: [5월 7, 2019, 5:53오전 UTC](https://meta.discourse.org/t/restoring-discourse-1-9-backup-onto-v2-3-0-beta9-184/117001/4 "2019-05-07T05:53:34Z")

</div>

> [@Stephen](#):
>
> Downgrading isn’t supported

OP is trying to restore a backup with a schema from 2017 so this is not what he is trying to do.

Might this be related to the fact that delayed column drops are working differently nowadays?

---

<div class="post-metadata">

### Author: ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [5월 7, 2019, 5:54오전 UTC](https://meta.discourse.org/t/restoring-discourse-1-9-backup-onto-v2-3-0-beta9-184/117001/5 "2019-05-07T05:54:28Z")

</div>

Fair enough, I was going by the title, which said he was upgrading to beta9 +184.

---

<div class="post-metadata">

### Author: ![oluies](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/oluies/32/120194_2.png) [@oluies](https://meta.discourse.org/u/oluies)
#### Post date: [5월 7, 2019, 6:56오전 UTC](https://meta.discourse.org/t/restoring-discourse-1-9-backup-onto-v2-3-0-beta9-184/117001/6 "2019-05-07T06:56:43Z")

</div>

Yes I was using v1.9 earlier and now I was planning to upgrade to v2.2.

I switched from Bitnami to a dedicated Docker install. Somehow latest+latest was installed. So I got v2.3.0.beta9+184 where the backup import failed.

So have to look up how to install a specific docker version

---

<div class="post-metadata">

### Author: ![oluies](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/oluies/32/120194_2.png) [@oluies](https://meta.discourse.org/u/oluies)
#### Post date: [5월 7, 2019, 6:57오전 UTC](https://meta.discourse.org/t/restoring-discourse-1-9-backup-onto-v2-3-0-beta9-184/117001/7 "2019-05-07T06:57:50Z")

</div>

Might be similar to this [Trouble upgrading from 1.9.0.beta11](https://meta.discourse.org/t/trouble-upgrading-from-1-9-0-beta11/105219)

---

<div class="post-metadata">

### Author: ![michaeld](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/michaeld/32/1594_2.png) [@michaeld](https://meta.discourse.org/u/michaeld)
#### Post date: [5월 9, 2019, 12:41오후 UTC](https://meta.discourse.org/t/restoring-discourse-1-9-backup-onto-v2-3-0-beta9-184/117001/8 "2019-05-09T12:41:01Z")

</div>

Yes! The solution basically is:

> to avoid this just run db:seed\_fu before you backup or upgrade Postgres

.

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [9월 9, 2022, 8:02오전 UTC](https://meta.discourse.org/t/restoring-discourse-1-9-backup-onto-v2-3-0-beta9-184/117001/9 "2022-09-09T08:02:03Z")

</div>



---

<div class="post-metadata">

### Author: ![RGJ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rgj/32/523185_2.png) [@RGJ](https://meta.discourse.org/u/RGJ)
#### Post date: [9월 9, 2022, 8:08오전 UTC](https://meta.discourse.org/t/restoring-discourse-1-9-backup-onto-v2-3-0-beta9-184/117001/10 "2022-09-09T08:08:35Z")

</div>


