# Database files are incompatible with server (updating inside Linode)

**URL:** https://meta.discourse.org/t/database-files-are-incompatible-with-server-updating-inside-linode/350727
**Category:** Support
**Created:** [February 5, 2025, 9:22pm UTC](https://meta.discourse.org/t/database-files-are-incompatible-with-server-updating-inside-linode/350727 "2025-02-05T21:22:39Z")
**Posts on this page:** 1
**Showing post:** 17

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [February 6, 2025, 8:17pm UTC](https://meta.discourse.org/t/database-files-are-incompatible-with-server-updating-inside-linode/350727/17 "2025-02-06T20:17:06Z")

</div>

You can copy the backup with scp/rsync. It’s easier and faster (unless you don’t know what that means).

You really want to create a **new** VM with a new OS (not a backup of a server with an out-of-date os) and move to it as described at [Move a Discourse site to another VPS with rsync](https://meta.discourse.org/t/move-a-discourse-site-to-another-vps-with-rsync/43812). The one that I just copied also had some ownership issues. You probably will too.

> [@kgreed](#):
>
> Strangely discbak.softwarebydesign.com.au (linode2) is currently re-routing to discourse.softwarebydesign.com.au (on the original linode)

If discbak is running the same image as the other server, I’d expect it to give you a certificate error (unless you visited `http://`) and then redirect to whatever is in HOSTNAME.

---

_[View the full topic](https://meta.discourse.org/t/database-files-are-incompatible-with-server-updating-inside-linode/350727)._