Not when it is so mission critical. Its operating system level stuff. Not datacenter stuff, just plain common housekeeping fundamentals.
The Backup release blog was so exciting from my recollection. Finally closing a wide gap to make it fly the realms of ‘hobby futzing’ to soar to something you could trust your home to. I admired the leap. Joining the big boys now. Even encryption.
You’re talking to somebody that subscribes to the Vatican Bank backup policy: Jesus saves, so should you! (Disclaimer added by me: with verified, restorable backups)
I don’t know whether to cry or be bewildered. A haiku is beyond me. Peace.
Edit: In hindsight, the blog and associated chat focused on backups, and there were only a few lines on restore.
The promise:
Restoring backups available to all installation methods
More good news—restoring backups is now supported across all installation methods!
Previously, only Home Assistant OS installations could restore backups. But with this release, this feature is now available for all installation methods! No matter how you run Home Assistant, even if you use our containers in a Docker environment, you can now restore your Home Assistant backups.
This also means you can restore backups from local storage, Home Assistant Cloud, or any future backup locations added through integrations.
As a matter of fact, all backup features, including everything we release today, will be available regardless of the installation method you are using. We want everyone to have a solid backup strategy.
An update has been made to the algorithm for restore.
For those that used the unofficial workaround to increase the size of the variable MAX_CLIENT_SIZE should possibly check that it has reverted in the fix so it does not cause instability for other routines that depend on the aiohttp subroutine.