Hi
I have deployed Metabase using GCP. Now to migrate it to production i need to take back of my application. I found that GCP deployed postgres DB as Metabsae Application DB. But i am not sure it deployed using docker or Java.
Please help me to understand how to take backup. I did use Pg_dump command to take backup but i am not able to connect it.
Below details in diagnostic info :
{
"browser-info": {
"language": "en-US",
"platform": "Linux x86_64",
"userAgent": "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:89.0) Gecko/20100101 Firefox/89.0",
"vendor": ""
},
"system-info": {
"file.encoding": "UTF-8",
"java.runtime.name": "OpenJDK Runtime Environment",
"java.runtime.version": "11.0.11+9",
"java.vendor": "AdoptOpenJDK",
"java.vendor.url": "https://adoptopenjdk.net/",
"java.version": "11.0.11",
"java.vm.name": "OpenJDK 64-Bit Server VM",
"java.vm.version": "11.0.11+9",
"os.name": "Linux",
"os.version": "5.4.0-1046-gcp",
"user.language": "en",
"user.timezone": "GMT"
},
"metabase-info": {
"databases": [
"bigquery"
],
"hosting-env": "unknown",
"application-database": "postgres",
"application-database-details": {
"database": {
"name": "PostgreSQL",
"version": "12.3 (Debian 12.3-1.pgdg100+1)"
},
"jdbc-driver": {
"name": "PostgreSQL JDBC Driver",
"version": "42.2.18"
}
},
"run-mode": "prod",
"version": {
"date": "2021-06-15",
"tag": "v0.39.4",
"branch": "release-x.39.x",
"hash": "f538050"
},
"settings": {
"report-timezone": null
}
}
}
Hi @Prajakta2021
So how did you deploy to GCP? Which guide or steps did you take?
The Diagnostic Info seems to indicate that you're using Docker for the Metabase app, but your data is stored in the application database, which is Postgres 12.3 in your case, so that's what you want to backup.
I cannot see which type of Postgres you have deployed - it might be Cloud SQL, if so then follow the guides on how to backup that:
https://cloud.google.com/sql/docs/postgres/backup-recovery/backups
Thanks. I will check the link.
Hi
I am able to connect metabase now. But somehow i am getting timeout error while connecting to Bigquery
below is from log :
[d24d1c09-d23e-435e-acc3-abd7490d9c4a] 2021-08-03T09:26:17+00:00 DEBUG metabase.server.middleware.log POST /api/database 400 5.0 s (0 DB calls)
{:valid false, :dbname "Timed out after 5.0 s", :message "Timed out after 5.0 s"}
[d24d1c09-d23e-435e-acc3-abd7490d9c4a] 2021-08-03T09:26:17+00:00 DEBUG metabase.server.middleware.log GET /api/database 200 3.0 ms (3 DB calls) App DB connections: 0/4 Jetty threads: 6/50 (6 idle, 0 queued) (54 total active threads) Queries in flight: 0 (0 queued)
[d24d1c09-d23e-435e-acc3-abd7490d9c4a] 2021-08-03T09:26:24+00:00 DEBUG metabase.server.middleware.log GET /api/util/bug_report_details 200 1.8 ms (1 DB calls) App DB connections: 0/4 Jetty threads: 6/50 (6 idle, 0 queued) (55 total active threads) Queries in flight: 0 (0 queued)
[d24d1c09-d23e-435e-acc3-abd7490d9c4a] 2021-08-03T09:30:06+00:00 DEBUG metabase.server.middleware.log GET /api/database 200 3.6 ms (3 DB calls) App DB connections: 0/4 Jetty threads: 6/50 (4 idle, 0 queued) (51 total active threads) Queries in flight: 0 (0 queued)
[d24d1c09-d23e-435e-acc3-abd7490d9c4a] 2021-08-03T09:30:06+00:00 DEBUG metabase.server.middleware.log GET /api/automagic-dashboards/database/1/candidates 200 6.5 ms (6 DB calls) App DB connections: 0/4 Jetty threads: 6/50 (4 idle, 0 queued) (51 total active threads) Queries in flight: 0 (0 queued)
[d24d1c09-d23e-435e-acc3-abd7490d9c4a] 2021-08-03T09:30:10+00:00 DEBUG metabase.server.middleware.log GET /api/setting 200 682.7 µs (0 DB calls) App DB connections: 0/4 Jetty threads: 8/50 (1 idle, 0 queued) (51 total active threads) Queries in flight: 0 (0 queued)
[d24d1c09-d23e-435e-acc3-abd7490d9c4a] 2021-08-03T09:30:10+00:00 DEBUG metabase.server.middleware.log GET /api/session/properties 200 3.8 ms (2 DB calls) App DB connections: 1/4 Jetty threads: 8/50 (1 idle, 0 queued) (51 total active threads) Queries in flight: 0 (0 queued)
[d24d1c09-d23e-435e-acc3-abd7490d9c4a] 2021-08-03T09:30:10+00:00 DEBUG metabase.server.middleware.log GET /api/setup/admin_checklist 200 7.6 ms (13 DB calls) App DB connections: 0/4 Jetty threads: 8/50 (1 idle, 0 queued) (53 total active threads) Queries in flight: 0 (0 queued)
[d24d1c09-d23e-435e-acc3-abd7490d9c4a] 2021-08-03T09:30:57+00:00 ERROR metabase.driver.util Database connection error
java.util.concurrent.TimeoutException: Timed out after 5.0 s
@Prajakta2021 That is caused by a firewall or networking problem. Make sure that Metabase is allowed to connect to your database and that any networking problems is resolved (firewall, DNS, etc).
ohh. is it. thank will connect with network team.