In its day it was installed by people who are no longer in the company and we don't have documentation, so we don't know if it is configured against mysql or if it uses its own database.
In /opt/Metabase we have these files:
total 189M
4.0K Apr 5 10:49 .
4.0K Aug 25 2021 ..
208K Apr 4 18:18 metabase.db.mv.db
187 Apr 4 18:17 metabase.db.trace.db
104M May 16 2017 metabase.jar
85M May 15 2017 metabase.jarold
4.0K May 15 2017 plugins
It seems that it uses the H2 database for the initial configuration, since it appears modified today.
The idea we have is to set this up from scratch, in a Docker. But we don't know how to do it. We have seen that it could be possible to take the metabase.db.mv.db file and put it in the Docker path. That with that the configuration would be migrated.
Hi @mgfeal
It definitely does not look like metabase.db.mv.db is where your data is. It's only 208KB.
Unless your instance was almost unused for many years, but then there should be almost no data either, so not even worth migrating.
Yes, the file was updated today, but could it be that you are messing around with things and possibly created that file at some point?
But before you do anything, then make sure to do a backup first.
@mgfeal Only on newer versions. You should see activity in the table query_execution if you try to run a query in Metabase, which will tell you if you are looking in the correct application database.