No… You have to make the backup on your own.
A assume you can use either ha command in the console or Google Backup. Not sure if the latter has comfortable way to backup selected component only (without need of backup profile creation)
Alright, I’ll skip the upgrade for now until I figure out how to solve it. A big thanks, I really appreciate the info!
@fedup you can use this if you need a specific file or files from an encrypted backup!
You should be able to re-structure the .tar file again from the decrypted archive and upload it to your new instance of HAss, I have not tried this yet but in theory it should work???
1 Like
No, none of that is true.
@Boilerplate4u If you use an automatic backup system (like google drive or samba share) before 2025.1 and after, all backups / restores from that system will work regardless of the version you’re going to.
@petro, you misunderstood the point. YES, the proposal to do a individual back-up of an add-on during update of this add-on is now a lost functionality.
I disagree with the radical solution taken to tackle a true risk for basic users = run out of space… I would have kept the functionality but simply set it as disabled by default, up to the user to consciously toggle the option during upgrade of an add-on.
4 Likes
I’m not missing the point, I’m answering boilers question. I’m not here to debate the feature, stop reading into my comments.
so why do you say it is not true then? I don’t get the rationale.
Because maxyms comment is not true in regards to existing automated backup addons.
3 Likes
ok this one
My OP was about (citation): automatic backup before add-ons/ha update
It’s not about automated backup addons.
see:
1 Like
This part is important.
If you’re talking about using the UI to update something, that was never part of the original conversation.
I never mentioned it this way (see above).
Yes, I warned Boilerplate, about pre-update auto-backup being removed.
2 Likes
I really wish someone could write a straightforward blog post, skipping all the marketing bs, that is clear, short, and to the point, explaining how the different backups fit together. Right now, it’s just a chaotic jumble of comments and counter-comments, making it nearly impossible to get a clear picture of the current situation.
1 Like
4 Likes
Great! Short and to the point, thanks! Why hasn’t the official blog been updated with this info!?
This is a major issue. Without the SSL folder, if you try to provision a new machine by restoring a backup (and the http integration refers to keys in the SSL folder), the restore will fail without explanation, and the installation will be unusable and inaccessible.
I wasted hours on this. I hooked up a monitor to the new machine, and it still wasn’t apparent until I looked carefully at the core logs and noticed that an error was generated by inability to locate the SSL key in the ssl folder (and thereafter failed to set up http).
The old backup commands do still make ‘Full backups’ with all folders… The same commands are used by the add-ons for backup, so they also still work.
Seem like a weird omission to not include those folders as a ‘Full’ Backup should include everything if you select that. I noticed the same before and it made me look into scripting it myself.
Still running these scripts daily and they do make full and unencrypted backups.
Local Backup
action: hassio.backup_full
data:
compressed: true
location: /backup
name: >-
Full backup {{
state_attr('update.home_assistant_core_update','installed_version') }}
and NAS backup with mount named backup
action: hassio.backup_full
data:
compressed: true
location: backup
name: >-
Full backup {{
state_attr('update.home_assistant_core_update','installed_version') }}
1 Like
really?
that then might be an issue worth complaining about.
an easy way to test backup restore would be welcome I think,
I always create backups, but I only check if I can restore them when needed.
I discovered this after the fact (i.e., if you make a backup by calling the backup service manually, everything works out fine). I had the misfortune to upgrade to the latest HA version with the new backup interface and then deciding to upgrade to a Raspberry Pi 5. I tried to provision the new RP 5 with a backup I made from the new backup UI, and that worked out very poorly.