I know that it will be discussed many times, but …
although I have been running OpenHab successfully in a Docker for several years now and also back up various volumes automatically on a weekly basis in the (free AWS cloud), I don’t really feel “safe” with the system.
You learn a lot by trying, but frustration often arises when this attempt results in a new installation.
In my case, I know exactly how to set up a fresh OpenHab in seconds, but not how to restore the backups with 100% certainty.
I would therefore really like two things:
A chapter on each add-on, where exactly its configurations are located and how to restore a backup of it.
A tutorial (based on Docker) to simulate D-Day.
In other words, simply shut down the existing containers and volumes and DO NOT change them, and then start up a system in parallel that looks and runs exactly the same.
For those rare bindings that have “extra” configuration (i.e appear in the third column of Settings) are in userdata/config/org/openhab/<nameofaddon>.config.
Everything else is configured via Things, Persistence, or Transformations which all gets saved to userdata/jsondb.
It would be redundant in the extreme to document this same information for each and every add-on.
Do nothing. It should just work, simple as that. If the version of the configs differ from the version of OH in the image (based on the contents of userdata/etc/versions.properties) the entry point script will automatically create a backup to user data/backup and perform the same upgrade steps that happen for apt/yum upgrades of OH (e. g. updating the files in user data/etc and running the upgradeTool).
You cannot have 2 instances of OH running off of the exact same volumes at the same time, but if you’ve set up the volumes according to the docs and have two identical copies, you don’t need to do anything at all. If you did, you couldn’t update the Image or run new containers with the same volumes.
Still nice and I guess I started with docker from your template
But in fact that I do not circle on a raspberry I have to touch whole SSD instead of SD-Card (just joking)
I don’t understand the question. What’s “whisper” in this context? What “model”?
If you follow the docs for how to run OH in Docker, you mount three volumes into the container: addons, userdata, and conf. Everything that OH needs for configuration and everything that OH would change are in those three volumes.
So to start up a new container with the exact same config, either copy those three volumes and start the container with those three volumes mounted, or just start a new container using those three volumes in place (only one container at a time should be using the same volumes in this case). That’s all there is to it. Everything is in those three volumes.
In fact there is more than you necessarily need in those volumes but having more than you need shouldn’t cause problems in this case.
