Unable to create backups - "Failed to to call /backups/new/full "

cornubot · August 24, 2024, 9:31pm

HA Green, running 2024.8.2, just restored a backup and installed latest version.

Unable to take backups of restored install.

UI gives the error:

“An error occurred while making backup, check job ‘a49f4820a4e14832a374e70afbad38d2’ or supervisor logs for details”

Supervisor logs says:

“2024-08-24 23:26:50.427 ERROR (MainThread) [supervisor.homeassistant.module] Preparing backup of Home Assistant Core failed. Check HA Core logs.”

HA Core logs says:

" Log Details (ERROR)

Logger: homeassistant.components.hassio
Source: components/hassio/websocket_api.py:135
integration: Home Assistant Supervisor (documentation, issues)
First occurred: 23:15:41 (3 occurrences)
Last logged: 23:26:50

Failed to to call /backups/new/full - An error occurred while making backup, check job ‘6918c7ad0b1f4352829d40d1dc7cffbf’ or supervisor logs for details
Failed to to call /backups/new/partial - An error occurred while making backup, check job ‘9fc4d197cdd840719a5efdbeddc16bde’ or supervisor logs for details
Failed to to call /backups/new/full - An error occurred while making backup, check job ‘a49f4820a4e14832a374e70afbad38d2’ or supervisor logs for details"

Been checking using SSH and there is no directory /backups/new/full, just the ordinary /backup (without s). Didn’t help to create them manually either.

Jolskutin · September 3, 2024, 12:23pm

Same issue with 2024.8.3

After updating to 2024.8.3 managed to do one backup, but cannot make any additional ones,
even after restoring to the first backup, cannot make new ones

Jolskutin · September 5, 2024, 6:23am

Updated to 2024.9.0, still no backup for core

Could it be that some file is corrupted?
My history does not work either so database gets corrupted???

Supervisor msgs:

2024-09-05 09:11:14.125 INFO (MainThread) [supervisor.api.middleware.security] /supervisor/info access from cebe7a76_hassio_google_drive_backup
2024-09-05 09:11:14.136 INFO (MainThread) [supervisor.api.middleware.security] /backups access from cebe7a76_hassio_google_drive_backup
2024-09-05 09:11:21.290 INFO (MainThread) [supervisor.homeassistant.core] Home Assistant Core state changed to APIState(core_state='RUNNING', offline_db_migration=False)
2024-09-05 09:11:21.291 INFO (MainThread) [supervisor.homeassistant.core] Detect a running Home Assistant instance
2024-09-05 09:11:21.292 INFO (MainThread) [supervisor.homeassistant.core] Successfully started Home Assistant 2024.9.0
2024-09-05 09:11:21.450 INFO (SyncWorker_2) [supervisor.docker.manager] Cleanup images: ['ghcr.io/home-assistant/qemux86-64-homeassistant:2024.8.3']
2024-09-05 09:12:05.327 INFO (MainThread) [supervisor.backups.manager] Backup cf9227d2 starting stage addon_repositories
2024-09-05 09:12:05.327 INFO (MainThread) [supervisor.backups.manager] Backup cf9227d2 starting stage docker_config
2024-09-05 09:12:05.328 INFO (MainThread) [supervisor.backups.manager] Creating new full backup with slug cf9227d2
2024-09-05 09:12:05.338 INFO (MainThread) [supervisor.backups.manager] Backup cf9227d2 starting stage home_assistant
2024-09-05 09:12:11.293 ERROR (MainThread) [supervisor.homeassistant.module] Preparing backup of Home Assistant Core failed. Check HA Core logs.
2024-09-05 09:12:21.527 INFO (MainThread) [supervisor.api.middleware.security] /supervisor/info access from cebe7a76_hassio_google_drive_backup
2024-09-05 09:12:21.535 INFO (MainThread) [supervisor.api.middleware.security] /backups access from cebe7a76_hassio_google_drive_backup
2024-09-05 09:13:57.147 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token

Core msgs:
Logger: homeassistant.components.hassio
Source: components/hassio/websocket_api.py:135
integration: Home Assistant Supervisor (documentation, issues)
First occurred: 9:12:11 AM (1 occurrences)
Last logged: 9:12:11 AM

Failed to to call /backups/new/full - An error occurred while making backup, check job ‘ed285824f792469f91537ab244e3bea1’ or supervisor logs for details

ReneSpit63 · September 12, 2024, 6:51am

I have the same issue.

Home Assistant Info:

Core 2024.9.1
Supervisor 2024.08.0
Operating System 13.1
Frontend 20240906.0

I start making a full backup.
Then I receive the error message:
afbeelding

In the backup directorie I can see that the backup process has started. A tar file has been created:

/backup ls -latr | tail -5
-rw-r--r--    1 root     root         10240 Sep 12 07:30 2826e5bd.tar
-rw-r--r--    1 root     root         10240 Sep 12 08:07 92ccd5be.tar
-rw-r--r--    1 root     root         10240 Sep 12 08:08 81089c1b.tar
drwxr-xr-x    3 root     root          4096 Sep 12 08:20 .
-rw-r--r--    1 root     root         10240 Sep 12 08:20 06e17a6b.tar

If you look into the supervisor log then you see exact the same error message.

/backup cat /config/home-assistant.log | grep d41bfabe72684e279fe2d3247afb57c0

2024-09-12 08:20:49.778 ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /backups/new/full - An error occurred while making backup, check job 'd41bfabe72684e279fe2d3247afb57c0' or supervisor logs for details

I read that many HA-users have the same issues. But I can’t find the solution for this issue.
Maybe for now there is no solution, but does anybody know a workaround for this issue? I tried to look into an old backup-tar-file. But there is only a very large json-file in it. So starting on the commandline a tar command is not a solution either.

ReneSpit63 · September 13, 2024, 7:49am

After a couple of restarts and activating sftp in ssh, I was able to make a backup.
afbeelding

DusBus · September 21, 2024, 6:02pm

I am having a similar issue:

## System Information

version | core-2024.9.2
-- | --
installation_type | Home Assistant OS
dev | false
hassio | true
docker | true
user | root
virtualenv | false
python_version | 3.12.4
os_name | Linux
os_version | 6.6.31-haos-raspi
arch | aarch64
timezone | Europe/Berlin
config_dir | /config

<details><summary>Home Assistant Cloud</summary>

logged_in | false
-- | --
can_reach_cert_server | ok
can_reach_cloud_auth | ok
can_reach_cloud | ok

</details>

<details><summary>Home Assistant Supervisor</summary>

host_os | Home Assistant OS 13.1
-- | --
update_channel | stable
supervisor_version | supervisor-2024.09.1
agent_version | 1.6.0
docker_version | 26.1.4
disk_total | 57.8 GB
disk_used | 4.5 GB
healthy | true
supported | true
host_connectivity | true
supervisor_connectivity | true
ntp_synchronized | true
virtualization | 
board | rpi3-64
supervisor_api | ok
version_api | ok
installed_addons | File editor (5.8.0), Node-RED (18.0.5), Advanced SSH & Web Terminal (19.0.0)

</details>

<details><summary>Dashboards</summary>

dashboards | 2
-- | --
resources | 0
views | 4
mode | storage

</details>

<details><summary>Recorder</summary>

oldest_recorder_run | 6 December 2022 at 18:46
-- | --
current_recorder_run | 21 September 2024 at 19:18
estimated_db_size | 458.59 MiB
database_engine | sqlite
database_version | 3.45.3

</details>

I recently had a SD failure and had to restore from an old backup (early 2023).

Jolskutin · September 26, 2024, 11:18am

2024.9.3 brought the problem back?
somehow all started to work with 9.2, BOTH database and backups
now after update to 9.3 and about a day after, the database is locked and backups does not work
(database locked means that all history is now flat lines, all charts shows flat, though the sensors gives the right value to the UI)

brxm · September 27, 2024, 1:07pm

Last week I had this problem too, when trying a full back-up. In the logs there were pointers at something in a ‘bellows’ dir going wrong. This bellows turned out to be part of ZHA/zigpy. Which I happened to have installed just a few days earlier. So, I deleted the ZHA integration, restarted HA and made a full back-up. Problem solved! Next step is to re-install ZHA and see what happens.

Part two: after re-installing ZHA the problem has returned. So there is definitely something in ZHA that causes a full back-up to crash.

Part three: after reverting the Zigbee Coordinator firmware to a previous version the problem was resolved and back-up completed succesfully.

duquedaniel · October 3, 2024, 10:04pm

I have the very same problem. Already upgraded to Core 2024.10.0.
Also had crashes after crashes and had to come back to a Full September backup. Now i cannot do any backup. Please advise.

Jolskutin · October 11, 2024, 7:17am

Still backups does not work, and database freezes:
2024.10.1 on W11 vmware

Clean installation of W11, VMware, and HA from a backup of 2024.9.3 (somehow that was a full backup)
everything worked for a while,
updated to 2024.10.1
tried to do manual backup → DID NOT Work … AND database freezes
Logs are no good:
Core: Failed to to call /backups/new/full…check job xxx or supervisor logs
Supervisor: Preparing backup of Home Assistant Core failed. Check HA Core logs

prior_philip · October 16, 2024, 11:16am

Right after updating core to 2024.10.2 and OS to 13.2
in one rush, it happens to me as well.
Either partial and full backups fail with no meaningful log messages.

As already mentioned in earlier posts, supervisor logs point to core logs and vice versa.

UPDATE:
It seems that- in my case - the Grafana Add-On as well was broken after OS and core update. I knew it and temporarily disabled the AddOn but that didnt help.

Finally uninstalling and reinstall Grafana did the trick. Backup, full and partial, again are functional.

Jolskutin · October 22, 2024, 6:15pm

there is another discussion ongoing in github:

github.com/home-assistant/core

i can't backup home assistant core

opened 11:40PM - 22 Aug 24 UTC

vothar

integration: hassio

### The problem i make a full backup before each new version of home assistan…t. my last full backup was from before 2024.8 version. Just after my last full backup (august the 6, 2024) and before trying to update to version 2024.8, i can't make anymore a full backup of home assistant. i can make a partial backup of the add-ons and Folders section, but when i try to do the partial backup (or a full backup) of the 'home assistant (2024.7.4)' section, i get the error **ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /backups/new/partial - An error occurred while making backup, check job 'b567fa7559c140588be5c2489fffddd8' or supervisor logs for details** and if i look at the supervisor log, i get **ERROR (MainThread) [supervisor.homeassistant.module] Preparing backup of Home Assistant Core failed. Check HA Core logs.** i'm using a RPi4 with HA on a SSD drive. - reboot HA, or Full reboot of the RPI didn't corrected the problem - i stopped the core, then delete the database to start a new one (to check if it's the database file that is corrupted) but the backup error is still there after that with the new database - thru samba, i can copy the files from the CONFIG directory without any error to my PC (so no corrupted files here). - after each failed backup, a new TAR files (10ko) appear in the BACKUPS directory. there is nothing in the archive. if i restore my last good full backup, home assistant is working without problem after the restoration, but i still can't make a new full backup (same error) after that any idea ? ### What version of Home Assistant Core has the issue? core-2024.7.4 ### What was the last working version of Home Assistant Core? core-2024.7.4 ### What type of installation are you running? Home Assistant OS ### Integration causing the issue backups ### Link to integration documentation on our website _No response_ ### Diagnostics information _No response_ ### Example YAML snippet _No response_ ### Anything in the logs that might be useful for us? ```txt HA core log error ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /backups/new/partial - An error occurred while making backup, check job 'b567fa7559c140588be5c2489fffddd8' or supervisor logs for details supervisor log error ERROR (MainThread) [supervisor.homeassistant.module] Preparing backup of Home Assistant Core failed. Check HA Core logs ``` ### Additional information ## System Information version | core-2024.7.4 -- | -- installation_type | Home Assistant OS dev | false hassio | true docker | true user | root virtualenv | false python_version | 3.12.4 os_name | Linux os_version | 6.6.31-haos-raspi arch | aarch64 timezone | America/Toronto config_dir | /config <details><summary>Home Assistant Community Store</summary> GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 5000 Installed Version | 1.34.0 Stage | running Available Repositories | 1461 Downloaded Repositories | 26 HACS Data | ok </details> <details><summary>Home Assistant Cloud</summary> logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | ok </details> <details><summary>Home Assistant Supervisor</summary> host_os | Home Assistant OS 13.1 -- | -- update_channel | stable supervisor_version | supervisor-2024.08.0 agent_version | 1.6.0 docker_version | 26.1.4 disk_total | 109.3 GB disk_used | 17.9 GB healthy | true supported | true host_connectivity | true supervisor_connectivity | true ntp_synchronized | true virtualization | board | rpi4-64 supervisor_api | ok version_api | ok installed_addons | Mosquitto broker (6.4.1), TheengsGateway (1.11.4), ZigStar TI CC2652P/P7 FW Flasher (0.4.0), Piper (1.5.2), ESPHome (2024.8.0), Advanced SSH & Web Terminal (18.0.0), File editor (5.8.0), Samba share (12.3.2), LMS Lyrion Music Server(Formerly Logitech Media Server) (8.5.2.0), Squeezelite (0.0.19), motionEye (0.20.0) </details> <details><summary>Dashboards</summary> dashboards | 25 -- | -- resources | 15 views | 23 mode | storage </details> <details><summary>Recorder</summary> oldest_recorder_run | August 22, 2024 at 17:52 -- | -- current_recorder_run | August 22, 2024 at 14:27 estimated_db_size | 23.21 MiB database_engine | sqlite database_version | 3.45.3 </details>

this issue is still ongoing with several people

Christianb233 · November 12, 2024, 10:08pm

Hello @ReneSpit63
Do you have definitively solved your issue after adding sftp: true ?