# Wrong version number on backup?

**URL:** https://meta.discourse.org/t/wrong-version-number-on-backup/154428
**Category:** Support
**Created:** [June 10, 2020, 4:39pm UTC](https://meta.discourse.org/t/wrong-version-number-on-backup/154428 "2020-06-10T16:39:19Z")
**Posts on this page:** 5
**Page:** 1

<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: [June 10, 2020, 4:39pm UTC](https://meta.discourse.org/t/wrong-version-number-on-backup/154428/1 "2020-06-10T16:39:19Z")

</div>

I’ve got a site running 2.5.0.beta2 ( [c4bc734b11](https://github.com/discourse/discourse/commits/c4bc734b11ba310086b1a7ab28f0d57e6a6030d8)). For . . . reasons . . . I need to keep it an its plugins pinned to a particular version.

I’ve built a new container on a staging site with Discourse pinned to a commit and each plugin `reset --hard` to the same commit that the current production site is running. Now I want to restore a backup to make sure that this actually did what I think it did.

The backup file is named `community-2020-06-10-163052-v20201303000002.sql.gz`

And restoring it fails because:

```plaintext
Validating metadata...
  Current version: 20200320193612
  Restored version: 20201303000002

```

or, for readability:

```plaintext
Validating metadata...
  Current version: 2020 03-20-19:36:12
  Restored version: 2020 13-03-00:00:02

```

I vaguely remember that there was a problem with backups having the wrong version number, but I can’t find it.

I guess I need to just rename it to community-2020-06-10-163052-v2020 **03** 03000002.sql.gz rather than community-2020-06-10-163052-v2020 **13** 03000002.sql.gz?

EDIT: Renaming the backup file worked, at least for the database-only backup. . .

EDIT 2: And I was then able to restore a renamed full backup.

---

<div class="post-metadata">

### Author: ![gerhard](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/gerhard/32/119479_2.png) [@gerhard](https://meta.discourse.org/u/gerhard)
#### Post date: [June 16, 2020, 10:07am UTC](https://meta.discourse.org/t/wrong-version-number-on-backup/154428/2 "2020-06-16T10:07:06Z")

</div>

Can you check if a plugin has a DB migration with “20201303000002” in the filename?

---

<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: [June 16, 2020, 12:44pm UTC](https://meta.discourse.org/t/wrong-version-number-on-backup/154428/3 "2020-06-16T12:44:07Z")

</div>

Darn. I don’t see such a filename or that string in any plugins. And it seemed like such a good explanation!

---

<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: [June 16, 2020, 1:47pm UTC](https://meta.discourse.org/t/wrong-version-number-on-backup/154428/4 "2020-06-16T13:47:39Z")

</div>

> [@gerhard](#):
>
> 20201303000002

A Google search for that string finds this topic, and this: [https://review.discourse.org/t/fix-ensures-migration-order-is-correct-27/10484](https://review.discourse.org/t/fix-ensures-migration-order-is-correct-27/10484)

Which pretty much explains what happened 🙂

---

<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: [July 16, 2020, 1:54pm UTC](https://meta.discourse.org/t/wrong-version-number-on-backup/154428/5 "2020-07-16T13:54:59Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.