Restore from backup appears stuck

Installation
1

I’ve been trying to restore from a backup for a whole day… and nothing appears to be happening.

I’m using the proxmox homeassistant VM - so not containerised.
The backup file is 1.9Gb.
I tried doing it during the onboarding and gave up after a few hours.
I then created an instance, uploaded the file via the GUI and initiated a restore. same result. HA logs appear to show it shutting down the Core. any commands from HA BK… say there is a job running… Restore in each case is just ‘core’, no adding selected.

image

I’ve read on some forums that restores can take… 10+ hours. this was last year though. so im wondering if there has been any changes. Currently using the latest versions…

image
image1280×494 15.3 KB

Is there any way to inspect the progress of this. CPU usage is 70% suggesting that it is doing something.

any idea?

2

If you are using an SD card with something PI based, the card may gave given up the ghost.
How do you know the CPU is at 70%, BTW?

3

It’s a proxmox VM running on a 32Gb RAM, SDD HDD, 3GHz system. I/O is not the problem. Proxmox can show me the stats.

image
image1504×634 73.3 KB

4

ha jobs info and ha supervisor logs -vf are probably your best way to check status/progress.

5

interesting… restore job reports progress ‘0’ after 15hrs… for several of the components… 100% for backup folder though…

# ha jobs info
ignore_conditions: []
jobs:
- child_jobs:
  - child_jobs:
    - child_jobs: []
      created: "2026-01-01T18:47:04.502816+00:00"
      done: true
      errors: []
      extra: null
      name: backup_folder_restore
      progress: 100
      reference: ssl
      stage: null
      uuid: 1686fb1da454401d919edd8faf77944b
    - child_jobs: []
      created: "2026-01-01T18:47:53.800809+00:00"
      done: true
      errors: []
      extra: null
      name: backup_folder_restore
      progress: 100
      reference: share
      stage: null
      uuid: 05e910e112d3480385ea004bfc959232
    created: "2026-01-01T18:47:04.502287+00:00"
    done: true
    errors: []
    extra: null
    name: backup_restore_folders
    progress: 100
    reference: 6e4f8441
    stage: null
    uuid: 6f11089de2374c7185cd9e7bf5774336
  - child_jobs:
    - child_jobs: []
      created: "2026-01-01T18:48:03.300173+00:00"
      done: false
      errors: []
      extra: null
      name: home_assistant_module_restore
      progress: 0
      reference: null
      stage: null
      uuid: fd9f699c415c447487dee47f9746a7bc
    created: "2026-01-01T18:47:54.206849+00:00"
    done: false
    errors: []
    extra: null
    name: backup_restore_homeassistant
    progress: 0
    reference: 6e4f8441
    stage: null
    uuid: 695c77ae53484aa7a826f9697958ddbe
  created: "2026-01-01T18:46:58.241180+00:00"
  done: false
  errors: []
  extra: null
  name: backup_manager_partial_restore
  progress: 0
  reference: 6e4f8441
  stage: home_assistant
  uuid: ddd579313b8045449e6033b7850cb670
6

Nearly 48hrs later it sprang to life.

This is far too long for a mission critical restore process.

I’m currently testing restore methods VM backup via snapshot or image and the HS restore. I’ll not bother with HA as it is too slow.

I’ll submit a ticket