Checkbox was activated and Automatic Backup 2025.1.1 was deleted.
This is why I said, adding a option of disabling encrypted backups with the warning that this will disable cloud backups, it covers them and you.
Honestly the forced encryption is bad enough, but taking away the autobackup before updates isā¦ mind-blowingā¦
8 Likes
Thereās also a setting just below it to delete ignored backups after X time. Do you have it set up maybe? Note that if you just put a number in there, itās number of seconds, so if you had something like 30, it deletes all ignored backups. The field accepts days in format ā123 daysā though.
To be clear, I havenāt tested it yet, I havenāt configured the new backups yet. If this doesnāt work correctly, I would write an issue in the github of the google backup add-on.
I think the best solution for now is to only use the add-on and to avoid the native backup. The only REAL problem is that it appears that the add-on is no longer maintained. Itās the perfect storm in relation to backups in HAā¦
SO I just went ahead, updated to .2 and configured the new automated backups. It tried to make the first backup immediately and failedā¦
Core log:
Rejestrator: homeassistant.components.backup
ŹrĆ³dÅo: components/backup/manager.py:790
integracja: Backup (dokumentacja, Problemy)
Pierwsze zdarzenie: 09:52:16 (1 zdarzenia)
Ostatnio zalogowany: 09:52:16
Error creating backup: Error getting backup details: Backup does not exist
Host log doesnāt have anything. Supervisor log:
2025-01-10 09:52:16.841 ERROR (MainThread) [supervisor.homeassistant.module] Preparing backup of Home Assistant Core failed. Check HA Core logs.
It hasnāt been updated for more than a year and at this point I think itās abandoned.
The problem is that the add-onās default backup location is āHA defaultā and thatās how most users will have it configured. So one must be aware of the problem and go into the add-onās settings to change the configuration from ādefaultā specifically to network storage. Otherwise Iām not sure where the add-onās backups will be stored.
I have just managed to create the new backup (after the first automatic try, second try triggered manually worked fine).
Iām using default locations.
In Google backup add-on, the HA core backup is correctly identified as ignored.
I can make a new backup in the google add-on. This is then shown in core as manual backup, same as the older backups I had.
Everything seems to work fine, Iām not sure what is the problem others have.
Does this update fix broken drag and drop in lovelace after the last update?
For people looking into alternate backup options and if you have a SMB/NFS share you can use on a NAS or something, you can easily still make unencrypted backups.
I have made two scripts which I trigger on a different moment each day. So I still have a backup locally and on the NAS per day which is unencrypted. You can also do this action in automation directly.
Local folder:
action: hassio.backup_full
data:
compressed: true
location: /backup
name: Full backup {{ now().strftime('%Y-%m-%d %H:%M') }}
and on NAS, backup is the name of my NAS mount in HA OS as Backup.
action: hassio.backup_full
data:
compressed: true
location: backup
name: Full backup {{ now().strftime('%Y-%m-%d %H:%M') }}
Also using the new Automatic Backup system with encryption enabled so I also have a local, NAS and cloud copy of that backup, just to be sure.
In the past I used the OneDrive Add-on, which can also be setup to ignore the back-ups it did not create itself. It still creates unencrypted backups if you donāt set a password. This is not a new feature and has been there for a long time.
5 Likes
Thatās correct. However, if you change the default storage location to a share rather than local, Samba Backup will no longer work.
Thatās not true, thatās what I have set up.
1 Like
Thatās not true. When you change the backup location within the add-on to a Samba one (previously set up in HA āstorage GUIā), the setting is honored.
Does anyone know if itās possible to have the NAS backup option backup into a folder/directory inside the Samba share rather than just at the root of the share. My NAS has a ābackupsā share which deals with a range of different devices - each either backing up via a package of some kind where itās clear which file belongs to which device, or into a folder within that share?
OK, then something must be wrong with me. I just changed the default storage location to the NAS (see screenshot) and triggered a Samba backup. See the result below.
[25-01-10 12:27:03] INFO: Backup running ...
[25-01-10 12:27:05] INFO: Creating backup "Manuelles SAMBA Backup 2025-01-10 12:27"
[25-01-10 12:29:49] INFO: Copying backup d6592472 (Samba_Backup_Manuelles_SAMBA_Backup_2025_01_10_12_27.tar) to share
[25-01-10 12:29:50] WARNING: d6592472.tar does not exist
[25-01-10 12:29:50] WARNING: Could not copy backup d6592472 to share. Trying again ...
[25-01-10 12:29:55] WARNING: d6592472.tar does not exist
Edit: Changed default to local again and samba backup finished without a problemā¦
You likely have both systems running in the same folder which is causing issues. Same thing I told you 4 days ago when you brought this up on the github issue.
Nope. Same share, but HA ā Folder 1 and Samba ā Folder 2