Upgrade Options to Maintain DB #2115
Replies: 1 comment 2 replies
-
|
Take a look at the docs on Storage, here (point 3) to get an idea of the database path and how to change it. But by default the database is stored in So if that's not your experience, can you post your docker container and Frigate config? |
Beta Was this translation helpful? Give feedback.
-
|
I believe I have solved my issue. I had initially moved the entire /media/frigate structure to a CIFS share, but kept running into DB locking issues. I then split that out so that just the clips and recordings were being directed to the CIFS share (as well as my config.yml so I could easily edit and restart):
This was working fine (keeping the DB on the container itself, but every update I would lose the old DB (unless I did some kind of manual backup and restore to the DB). I just reconfigured my Docker compose file to redirect the /media/frigate directory to a perpetual volume on the Docker host and it does seem to be working and should allow me to keep the DB files after an upgrade, as well as my clips/recordings on the CIFS share, which is what I want:
|
Beta Was this translation helpful? Give feedback.
-
|
Seem most recent docs about storage: https://docs.frigate.video/installation#storage |
Beta Was this translation helpful? Give feedback.
-
Hi all,
Any recommendations on how to best transition/save existing DB's when upgrading to a new image? I have just been rebuilding my container with the new image each time, but was thinking it would be nice to keep the DB if possible (my clips and snapshots are stored on a network share, but the DB is running locally).
Or is it recommended to start with a fresh DB when moving to each new version?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions