-
Notifications
You must be signed in to change notification settings - Fork 602
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New backup format in latest supervisor breaks partial restore #4909
Comments
hm, somehow, a supervisor update from february 16th popped up where the backup Format was changed. could be related to my issue. testing this today. |
Still same error. I was already wondering that there were no changes to the restore logic in the PR where the backup Format changed. is that related? can some1 verify? |
Core 2024.3.0 I got "Not a gzipped file" error thrown in supervisor when tried full restore. Partial backup on another hand worked (upload was done via front-end) and I was able to restore to an earlier addon versions. |
From tar archive's backup.json
|
That looks like a different problem since 2023.11.6 didn't have any of the newer changes |
I got same problem (same supervisor logs), backups march 06 and january 22 (20224) cannot be restored using HA OS 12.0 Configuration: RPi4 32 bits, the backup .tar size os about 3.7GB. The tar file is healthy, I can read it. |
I also noticed I can't restore previous backup as (I suppose) supervisor cannot be downgraded (even one with size 1.7GB from june 2023 and HAOS 10.2). Too bad, my HA is down, I am going to try a manual restore. |
Restoring a newer backup on a older Supervisor is prevented, but the reverse should not be prevented. So, restoring your backup from June 2023 should work. What is the error in that case?
Did you upload the Backup in some way to that instance? Maybe a corruption during upload? 🤔 |
What I can say is I was able to restore backups from march 06 and january 22 2024 in a VM for virtual box (Windows). |
I do not think that it is a currupted file. I had this for partially restoring from a full backup. restoring the backup as a whole works besides the timescaledb addon where I had the issue mentioned above. since that postgres holds my whole homeassistant entity states, that addon is huge and thus it seems to not properly restore. Thats why I wanted to restore only that addon as a partial restore... |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
Same issue for me:
The actual structure looks like that:
I also tried to re-compress the backup and upload it, without success. |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
Describe the issue you are experiencing
Hey there,
I have a full backup which I do want to restore. Due to its sheer size, I did a normal setup, installed the SSH addon and uploaded the backup to the backup folder via SCP.
I was able to select that backup to restore my machine, but the addon which takes the biggest amount of space was not restored (which is my timescaledb). So somehow, the whole machine was restored and most of the stuff is running besides those integrations depending on the database (which is within the timescaledb addon which was not restored).
Now I can at least use most of my integrations, etc. but I want to restore my addon. So what I tried was to partially restore the addon only now, since all the other stuff is already properly setupped.
When I try to partially restore, I get an error during after quite some time which tells me to have a look in the supervisor logs.
I've attached these log lines below.
Please note that it is the exact same backup which does restore all the other stuff, so I have absolutely no clue what that means "not a gzipped file" as it is definitely a GZIP file...
Any ideas on what I can do to restore my (fairly big addon) backup?
What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Home Assistant Operating System
Steps to reproduce the issue
Anything in the Supervisor logs that might be useful for us?
System Health information
System Information
Home Assistant Community Store
Home Assistant Cloud
Home Assistant Supervisor
Dashboards
Supervisor diagnostics
config_entry-hassio-95fec82dcd96f58467255ee49ee0f874.json
Additional information
I was able to restore a kinda similar large backup (also 6GB) back in december. I haven't tried that backup file yet, might do that somewhat later, but it is probably not a size problem.
The text was updated successfully, but these errors were encountered: