# Problems restoring from weaviate backup

**URL:** <https://forum.weaviate.io/t/problems-restoring-from-weaviate-backup/2489>\
**Category:** Support\
**Created:** [May 27, 2024, 12:45am UTC](https://forum.weaviate.io/t/problems-restoring-from-weaviate-backup/2489 "2024-05-27T00:45:31Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![j1mmc1v3r](https://avatars.discourse-cdn.com/v4/letter/j/9fc29f/32.png) [@j1mmc1v3r](https://forum.weaviate.io/u/j1mmc1v3r)\
**Post date:** [May 27, 2024, 12:45am UTC](https://forum.weaviate.io/t/problems-restoring-from-weaviate-backup/2489/1 "2024-05-27T00:45:31Z")

</div>

### Description

Using python weaviate-client 3.26.0, I took a back-up of my weaviate data using the following:

> def save\_weaviate\_data(server, timestamp):  
> backup\_id = server + ‘\_’ + timestamp  
> client = weaviate.Client(“[http://localhost:8081](http://localhost:8081)”)  
> result = client.backup.create(backup\_id=backup\_id, backend=“s3”, wait\_for\_completion=True)  
> print(result)

When I try to restore the data, I get the following error:  
weaviate.exceptions.UnexpectedStatusCodeException: Backup restore! Unexpected status code: 422, with response body: {‘error’: [{‘message’: ‘unable to restore backup as it was produced by a higher version: 2.1 \> 2.0’}]}

Any suggestions would be most helpful

### Server Setup Information

- Weaviate Server Version: 1.23.15
- Deployment Method: docker container image: semitechnologies/weaviate:latest
- Multi Node? Number of Running Nodes: 1
- Client Language and Version: python weaviate-client 3.26.0

### Any additional Information

---

<div class="post-metadata">

**Author:** ![j1mmc1v3r](https://avatars.discourse-cdn.com/v4/letter/j/9fc29f/32.png) [@j1mmc1v3r](https://forum.weaviate.io/u/j1mmc1v3r)\
**Post date:** [May 29, 2024, 4:11am UTC](https://forum.weaviate.io/t/problems-restoring-from-weaviate-backup/2489/2 "2024-05-29T04:11:18Z")

</div>

Aha - I have fixed this now. Turns out, I was trying to restore data to a different weaviate instance but that target instance was a different version that the one I did the back up from. Updated the target weaviate instance version and it all just worked. Hope this helps anyone else that finds themselves in the same boat. Worth noting that my docker-compose file was using the weaviate:latest image - when I created the target instance, the “latest” image was at a higher version.

---

<div class="post-metadata">

**Author:** ![Dirk](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/dirk/32/46_2.png) [@Dirk](https://forum.weaviate.io/u/Dirk)\
**Post date:** [May 29, 2024, 6:27am UTC](https://forum.weaviate.io/t/problems-restoring-from-weaviate-backup/2489/3 "2024-05-29T06:27:47Z")

</div>

> [@j1mmc1v3r](#):
>
> Worth noting that my docker-compose file was using the weaviate:latest image - when I created the target instance, the “latest” image was at a higher version.

please don’t use `latest`🙂

---

<div class="post-metadata">

**Author:** ![rjalex](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/rjalex/32/807_2.png) [@rjalex](https://forum.weaviate.io/u/rjalex)\
**Post date:** [July 22, 2024, 5:47pm UTC](https://forum.weaviate.io/t/problems-restoring-from-weaviate-backup/2489/4 "2024-07-22T17:47:06Z")

</div>

Using latest is a recipe for disaster 🙂 Always use a know version/tag so things are repeatable.