Sorry - my fault. Just found the “missing” option again:
I have the same issue with the Samba_Backup
WARNING: 68819390.tar does not exist.
So forget that.
To get auto Backups to work to a NAS or Local I have setup two different easy automations instead.
You can trigger these manually by an input_button created with the ‘helper’ and a Custom Button on a dashboard or at a Preset time that suits me and directed to NAS or local/backup, unencrypted.
Here is my aurtomation to go to my NAS
alias: Manual Backup NAS
description: Manual Backup
triggers:
- trigger: state
entity_id:
- input_button.manual_backupnas
conditions: []
actions:
- action: hassio.backup_full
metadata: {}
data:
compressed: true
homeassistant_exclude_database: false
location: backhass130
name: >-
FULLBackup {{
state_attr('update.home_assistant_core_update','installed_version') }}
time {{ now().strftime('%Y-%m-%d, %H:%M:%S') }}
mode: single
So I now have some good options:-
- manually triggered to NAS unencrypted
- manually triggered to my local/backup unencrypted
- time triggered, (my time not 4:45), daily to my NAS unencrypted
- Auto Encyrpted to my local/backup (via the Auto HA at 04:45 time)
Let’s just hope the supergod’s in the control room don’t break these options… please.
Is it possible to use the backup restore for conversion from
a) RPI 4b with rasbian os 64 and 64 hass docker for rpi TO
b) RPI 4b with hass os
I did not succeed…(me)
What i did:
- source: made a backup in the nabu cloud from my production rpi4b with HASS 64 rpi docker with several HACS integrations
- target: installed an extra (spare) rpi4b with homeassistant os image
- target: connect the device to the same nabu account as the source
- target: selected (click) on the new backup for restore
then i get unknown error - target: try to download the backup from the cloud
then i get Site is not available in the browser - source: i downloaded the bck file from the source to my pc
- target: uploaded the bck file to the target from pc
- target: clicked on the uploaded bck file to recover, entered the key,
- target: it shows: restoring for 2 seconds (strange is a large file 350mb)
- target: it shows: restarting: waited 30 minutes, no screen, so rebooted
- target: old situation shows
Is this scenario anyway a possibility and if not, what is the easiest way to convert from my source 64 with 64 docker to target with hass os ?
Fixed exact this problem by changing the option as above mentioned to local as default location. Now the automatic native backups AND Samba Backup are working as expected. No need for any automation…
Hi, I just checked the backups created by this, in “Home Assistant Google Drive Backup” add-on. One thing I noticed. Compared to a backups that I created in this add-on, the ones that were created by this new Backup feature are marked as “partial backup”, while the ones created from the add-on are “full backup”. The difference is The missing folders when using HA Backup feature are: “Local Add-on Folder” and “SSL Folder”. Is there any plan to include these folders in backup data (chance to enable this in “Backup data”? Thank you!
PSA: An old/alternate interpretation of the 3,2,1 data protection strategy is that you should use two different backup formats to protect against a bug in your software that makes your backups unrestorable.
There is more coverage in the other thread about a flaw in pvizeli’s secure tar format where there is a small but realistic chance that backups won’t be restorable.
See 2025.1: Backing Up into 2025! - #351 by petro
So it’s a good idea to make sure you have regular copies of your configuration/data that are produced by something other than Home Assistant backups.
4 Likes
I mean combination:
- installed samba share
- installed samba backup
But now i remember that i did some testing with mounted synology backup share inside my test HA and when i moved default backup location to syno share i’ve got such an error. But that was just a test - in practice i don’t have synology share, and my HA backup location is at default (inside HA). As said, samba backup can connect to synology by itself, without mounting share into HA
That’s clear. Luckily I now have a solution for both. HA automatically backs up to the network share and Samba Backup uses its own share. Luckily it works again after finding the setting.
The samba backups, can they actually be used to restore? Since they are not created with the new encryptep backup system?
Backups and restores were not changed. Just an automated gui was added, it happens to only allow encrypted backups.
4 Likes
It feels like the removal of the backups before performing updates is being downplayed. This seems like a huge change to me. Even if I never use one, it makes me much more comfortable performing updates. With that change gone, I am going update far less often.
4 Likes
No one has down played that. Not sure where you get this idea from. I was answering Fabio’s question.
2 Likes
Fixed. Just had to clear cache.
All of my measurement units(?) are missing after the update. ex. °F, %
1 Like
In firefox I can’t set the number field for days of backups
in chrome it works.
edit:
even worse,
after setting up the backup it keeps failing.
Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/connection.py:315
integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 21:22:26 (2 occurrences)
Last logged: 21:26:46
[546588852576] Error handling message: Error creating backup: 'BackupManager.do_backup_partial' blocked from execution, system is not running - freeze (home_assistant_error) Bart from 192.168.180.154 (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36 Edg/131.0.0.0)
[546586622512] Error handling message: Error creating backup: 'BackupManager.do_backup_partial' blocked from execution, system is not running - freeze (home_assistant_error) Bart from 192.168.180.154 (Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:133.0) Gecko/20100101 Firefox/133.0)
[Edit 2:] after a host reboot, it works
<ctrl>F5 to clear cache and refresh
That did it. Thanks
I agree, god this thread is soo negative… (some have relevant comments though)
Good that they have started implementing this, works for me as expected and advertised. I will still use Google Drive Backup in parallel for my files and also copy them to a local server until they get all the features in place.
1 Like
if it’s mandated to be encrypted, I’m out….
Skipping this one…
2 Likes
I noticed this evening that all of my sensors are missing data from ~4:45AM to about 11AM for today only. At around 11AM, all of my energy consumption sensors reported crazy negative numbers, which completely messed up my energy dashboard since there was no data for hours and then sensors that should never go negative were now reporting negative values.
The only changes I’ve made to environment this week was the upgrade to 2025.1 and enabled this new backup system (that fails to upload to cloud due to my backup size).
I recognize this is not a support thread, but I honestly do not even know where to begin in preparing any sort of bug filing on this. It just seems super coincidental that at the time this new backup feature starts, the recorder stopped recording sensor data…and then added significant negative numbers when recording resumed.
Since discovering this, I’ve disabled the new backup feature (I was previously using OneDrive), manually changed all of the negative values to zero at 11AM today, I’ve added several exclusions to my recorder configuration (in attempt to lower db size), and purged/repacked db. But please let me know if anyone has any pointers on what information or logs to grab to file a bug to the right place. This was a painful issue with no clear reason why or how.
Does anyone else have problems with automatic backups? A manual backup is successful.
The automatic backup could not be uploaded to the configured locations cloud.cloud.
1 Like