I get that an actual progress bar would be very hard to code seeing as it might be the database or an addon or whatever and you cannot take into account everything.
A way to give you an update would be to show whats happening in view only console window. Or a simple steps view like 2N does for example (linux based):
My restore is running. Found out that if you have a monitor and keyboard attached, you can use the cli to do: jobs info
It gives you running jobs. If you see an empty list, it is not doing anything. If it is busy, you see what jobs it finished and which are running (such as restore addons)
I did somehow manage to restore my backup of 5 GB. However, it took several hundred of GiB:s flowing to HA. What HA did with all of the GiB:s is unknown to me.
It took several hours for me to get to the screen where I could choose to restore everything or choose what to restore. This time, I choose to restore everything and after that it did not take that long before I had my backup up and running.
I do not know exactly what did it, but now I can restart HA without having to kill VirtualBox. I guess some of these settings did the trick in VirtualBox.
After a couple of hours trying the new HA out, it seems that I have got the same problem. I cannot restart HA without killing the process on my host. I guess it must be something with VirtualBox. All I tried to do was to add InfluxDB, which did not restore correctly and I had to supply it with a database name/password.
Well, now I know a bit more than I did a couple of days ago. I will try KVM instead.
I’m not sure you will get many answers in this section as it’s for feature requests rather than technical assistance. Maybe @moderators can move it for you ?
Not really the indicated feature but a way you can know if the restore process is alive, is by opening up the browser console and heading to the network tag, the backup process seem to ping the browser every certain amount of seconds, not perfect but at least it does let you know something is happening.
Having UI output and/or a log of the restore process could also enable optimizing the whole process. I can’t help but think why restoring a 800MB backup on a pi4 should take multiple hours.