Cannot restore Settings from backup without database

[tjorim]

Checklist

• I have updated to the latest available Home Assistant version.
• I have cleared the cache of my browser.
• I have tried a different browser to see if it is related to my browser.
• I have tried reproducing the issue in safe mode to rule out problems with unsupported custom resources.

Describe the issue you are experiencing

I'm trying to restore my Home Assistant 'Settings' in the new backup UI. (I assume this is the configuration, both UI and yaml files). But don't want to restore 'History'. However, I get an error almost straightaway it cannot do that without database.

Describe the behavior you expected

Let me restore my Settings without History, why have the option otherwise? Database version is even the same if that's a concern.

Steps to reproduce the issue

1. Make a backup or choose an existing one (manual or automatic)
2. Try to restore the Home Assistant settings
3. Watch the error

What version of Home Assistant Core has the issue?

core-2025.1.0b3

What was the last working version of Home Assistant Core?

No response

In which browser are you experiencing the issue with?

Google Chrome Version 131.0.6778.205 (Official Build) (64-bit)

Which operating system are you using to run this browser?

Windows 11 Version 23H2

State of relevant entities

No response

Problem-relevant frontend configuration

No response

Javascript errors shown in your browser console/inspector

Nothing relevant in DevTools Console

Additional information

This is also written to the HA logs:

 Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/connection.py:315
integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 22:39:53 (2 occurrences)
Last logged: 22:40:30

[546284361408] Error handling message: Cannot restore Home Assistant without database (home_assistant_error) Jorim Tielemans from 127.0.0.1 (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36)

[bramkragten]

This seems like a backend restriction, will discuss with them

[Sergey842248]

Same problem here