How to upgrade metabase without losing old data?
How are you running Metabase? If you’re using the stand-alone .jar its as easy as stopping the process, downloading the new .jar, replacing the old one and starting it again.
Someone else will have to weigh in for the docker or aws versions.
@adunbrook is right. To add to that:
-
Make sure you have a valid backup of your database (if you’re running Docker and still running on the default H2 database inside the container now is the time to copy the application database!)
-
Read relevant parts of this section in the fine manual: https://metabase.com/docs/latest/operations-guide/start.html#upgrading-metabase
All excellent points! Especially reading the MetaBase documentation on this, would suck to lose your MetaBase db and have to set it all up again.
The how to upgrade page has a link to a document titled:
Upgrading AWS Elastic Beanstalk deployments
However the link is broken. Anyway it could be reinstated?
I’m a non techie (more a product manager) and wary of upgrading without a step-by-step
Sorry about that broken link! We’ll get that fixed, but in the meantime, here’s a link that works: https://metabase.com/docs/latest/operations-guide/running-metabase-on-elastic-beanstalk.html#deploying-new-versions-of-metabase
Hi @maz
Followed the instructions and got an error.
Log pasted below
Hi, @akash47. Hmm, with my limited technical knowledge, it looks to me like you’re having problems due to a lack of memory. Maybe @camsaul or @sameer could provide some more specific guidance.
@akash47 What instance size are you using? I’ve never seen that error, and my guess is that it’s EC2 being EC2 (i.e. somewhat flakey on occasion).
If it doesn’t work, you can try killing that instance, letting auto-healing bring a replacement back up and then trying to upgrade again.
While beanstalk is stateless InTheory, InPractice there’s all kinds of cruft that can build up.
Hi @sameer
I’m using a t2.micro instance.
This bit here though:
If it doesn’t work, you can try killing that instance, letting auto-healing bring a replacement back up and then trying to upgrade again.
I’m wary to do that
In fact I don’t know where to begin. I’m a product manager who knows SQL. I’m very familiar with Tableau, though I’m using Metabase to help a small business get more data driven. And It’s perfect for that.
But I’m not a techie and the only way I managed to get it installed was via a help thread on this forum.
So I’m wary of killing the instance
The link is dead again.
the bad link should be: