-
Hi all, I fooled around with my docker host and I wonder if there is a good strategy to backup solectrus locally? Maybe because I am an absolut newbie I wonder what I would need to backup. For sure my docker-compose and .env are save (a simple copy to my notion and versioning in portainer) and my docker host is getting exported once a day to a NAS with cloud sync. For me it was not enough since I wanted a backup of the data & settings (like electricity prices). I was able to successfully backup influx once a day via cron ( So I wonder how and what are you backing up and where solectrus is storing its data & settings :) Thanks for sharing and explaining (remember I have no experience with influx and whatever technology is behind solectrus). Kind regards |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 4 replies
-
Great that you have found a way to back up InfluxDB with the CLI. This is the right way to create a local backup of your measurement data.
This seems to be caused by caching. Every InfluxDB query is cached in Redis for performance reasons. So, when you delete the InfluxDB volume, the cache results are still present. If you change data in InfluxDB in an unusual way (e.g. deleting the volume, importing historical data, etc.), you must then clear the Redis cache by running this command:
BTW: For backing up InfluxDB to Amazon S3, you can use this tool: For PostgreSQL (electricity prices and settings) there is a similar tool: I use both to back up the live demo once a day. |
Beta Was this translation helpful? Give feedback.
-
I just created "official" scripts to do backup & restore: |
Beta Was this translation helpful? Give feedback.
Great that you have found a way to back up InfluxDB with the CLI. This is the right way to create a local backup of your measurement data.
This seems to be caused by caching. Every InfluxDB query is cached in Redis for performance reasons. So, when you delete the InfluxDB volume, the cache results are still present.
If you change data in InfluxDB in an unusual way (e.g. deleting the volume, importing historical data, etc.), you must then clear the Redis cache by running this command: