Don’t necessarily migrate to the new instance; create a temporary instance, restore onto it, check it all works OK, then create a new container in the original location, shut down the old one, and restore the upgraded backup. Not that that should be any different, functionally, to doing an in-place upgrade, but at least you won’t blow up the live site if things don’t go according to plan (which, given how old that instance is, I wouldn’t rule out).
mpalmer
(Matt Palmer)
8
Gerelateerde topics
| Topic | Antwoorden | Weergaven | Activiteit | |
|---|---|---|---|---|
| What to Expect When Rebuilding Discourse | 10 | 531 | 5 november 2025 | |
| Manually create and restore Discourse backups | 13 | 16732 | 16 juni 2022 | |
| How to backup Discourse + Database from Console? | 2 | 1067 | 8 april 2019 | |
| Move Discourse to a new server without setting up the web UI first? | 11 | 3166 | 3 september 2022 | |
| How to upgrade if `/var/discourse` has only `shared` and is not git repo | 12 | 1709 | 24 juli 2020 |