You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[FR]: Enhancement request- Support/Integrate calling external backup engine to support HA Core backup of InfluxDB & MariaDB (or any other rrelevant)
#99
Open
taw123 opened this issue
Apr 12, 2023
· 0 comments
Is your feature request related to a problem? Please describe.
First thanks for your efforts on this backup service extension, I have been using it since you initially launched it.
While those who use HASSIO/Supervised have the ability to backup their MariaDB based HA data automatically using this service (recent bug in HA note withstanding), those of use who deploy HA in Docker (HA Core) do not seem to have the same abilities.
I recently moved from internal/Alchemy to MariaDB (and added InfluxDB for long-term data retention), and as such thoughts now turn to backup. I found a great looking container with long-term positive track record for both reliability and active development, docker-db-backup
It looks like it can not only be automated itself, but be invoked directly to perform said backups.
So my thought was this, rather then you potentially being asked by every Tom, Dick, and Harry to extend support to backing up their particular favorite HA related DB, perhaps you could simply provide integration with this and potentially cover ALL cases while leveraging a best of class service with an already extensive user base.
I was a s/w Engineer and later Product Manager for over 25 years and am willing to assist in any way that would be helpful to you should that make sense. Just trying to do what I can here. As wee said in the early days of the IETF- We today all stand on the shoulders of the giants that came before us....
Let me know what you think, and thanks again for all you have ALREADY done (now if only I could get the "real" names for each of the backups written to the file system I could check another item of my long term list)-- lol
--T
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
First thanks for your efforts on this backup service extension, I have been using it since you initially launched it.
While those who use HASSIO/Supervised have the ability to backup their MariaDB based HA data automatically using this service (recent bug in HA note withstanding), those of use who deploy HA in Docker (HA Core) do not seem to have the same abilities.
I recently moved from internal/Alchemy to MariaDB (and added InfluxDB for long-term data retention), and as such thoughts now turn to backup. I found a great looking container with long-term positive track record for both reliability and active development, docker-db-backup
It looks like it can not only be automated itself, but be invoked directly to perform said backups.
So my thought was this, rather then you potentially being asked by every Tom, Dick, and Harry to extend support to backing up their particular favorite HA related DB, perhaps you could simply provide integration with this and potentially cover ALL cases while leveraging a best of class service with an already extensive user base.
I was a s/w Engineer and later Product Manager for over 25 years and am willing to assist in any way that would be helpful to you should that make sense. Just trying to do what I can here. As wee said in the early days of the IETF- We today all stand on the shoulders of the giants that came before us....
Let me know what you think, and thanks again for all you have ALREADY done (now if only I could get the "real" names for each of the backups written to the file system I could check another item of my long term list)-- lol
--T
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: