Migrate Metabase from one server to another

Get Help
1

Hi there,

I need to migrate metabase vertion 0.47.3 from one to another server. We are using production ready installation with Postgres Sql, metabase itself is deployed as a Docker Container.

I backued up metabase application database, and sucesssfuly restored it to another instance, I can see all the data in tables by queryng tables.

Now, I pulled the docker image v.47.3 and build docker run command like this:

docker run -d -p 5000:3000
-e "MB_DATA_TYPE=postgres"
-e "MB_DB_DBNAME=metabasedb_new"
-e "MB_DB_PORT=5432"
-e "MB_DB_USER=metabase"
-e "MB_DB_PASS=metabase123"
-e "MB_DB_HOST=192.168.15.23" --name metabase metabase/metabase:v0.47.3

Typing the address in the url I get the setup screen, as if I would by first time setup. Why is this happening.

Some more info: I installed Postgres and metabase.jar on my laptop. Run restore of the Metabase applicationdata, and let metabase.jar connect to it. I ve got everyting up and running, my dashboards, questions, users stc. were all there.

On the docker version it does not work!!

1 Like
2

Solved, after whole day of trying. Here are the steps that worked for me.

  1. On the new server:, create new database in Postgres

  2. Install Metabase in Docker, let it point to newly created postgres database

3.Open Metabase in browser, setup wizard starts, finsh setting the new Metabase instance

  1. Stop Metabase containser

  2. From pgAdmin drop the postgres database

6.Create new postgres database with the same name as in step one

  1. Restore application database from psql to database created in step six

8.Start Metabase container

9.Open browser and login to Metabase

For some reason, it does not work in reverse order i.e, restore application database, and then create metabase container and reference to the restored database. In this case it starts the Metabase setup wizard and sets the Metabase as new installation, without existing questions, dashboards etc.

1 Like
3

I also struggled with migrating Metabase v0.49.13 from one cluster to another (Nomad to K8s). Then I followed your steps, and they worked for MySQL too.
Surprised that Metabase hasn't published any docs about migration from one server (cluster) to another.
Thank you, @dmerdan

4

it's just as simple as doing a backup and restore of a database backup

5

Can I ask you a question? How did you stop the pod, or did you simply connect it to the new migrated database?

6

Just simply stop the metabase service, then all pods killed.

7

Hi everyone,

I’m working on an app to migrate dashboards (and all their components) from one open-source project to another. So far, I’ve made significant progress: I can successfully migrate complex cards/questions along with all their dependencies, keeping the formatting intact. It took me about 14 hours of work yesterday to get to this point.

The next step on my roadmap is tackling dashboard migrations.

If you’re interested in contributing to the development of this app or have ideas to share, I’d love to collaborate! Let me know if you’d like to get involved or if you have suggestions to improve the process.

Thanks!