#C01HWQ1R0BC@Nagesh Bansal Hi Team
I am planning to upgrade our SigNoz deployment to the latest version with helm chart. Before that, I want to take a backup of the existing
signoz.db
(SQLite database) and use it to restore data (users, dashboards, alerts, etc.) after reinstalling the latest SigNoz version.
My plan is:
1. Take a backup of the
signoz.db
file from the current
query-service
pod.
2. Uninstall the existing SigNoz Helm release.
3. Install the latest SigNoz Helm chart.
4. Use an initContainer or another mechanism to copy the backed-up
signoz.db
into the new
signoz
pod (replacing the default DB).
Can you please confirm if this approach is supported in our setup?
v
Vibhu Pandey
06/27/2025, 6:26 AM
Works 👍
t
Talari Dhanunjaya
06/27/2025, 6:39 AM
@Vibhu Pandey But getting below error
" {"level":"fatal","timestamp":"2025-06-27T063415.659Z","caller":"query-service/main.go:147","msg":"Failed to create signoz","error":"no such column: \"created_at\"","stacktrace":"main.main\n\t/home/runner/work/signoz/signoz/ee/query-service/main.go147\nruntime.main\n\t/opt/hostedtoolcache/go/1.23.9/x64/src/runtime/proc.go272"}"
do i need to disable signoz-schema-migrator ??
v
Vibhu Pandey
07/02/2025, 1:49 PM
Copy code
Can you exec into the signoz container and run:
apk add sqlite
sqlite3 /var/lib/signoz/signoz.db
> SELECT * FROM migration
SigNoz is an open-source APM. It helps developers monitor their applications & troubleshoot problems, an open-source alternative to DataDog, NewRelic, etc.