"Uploaded snapshot is too large" When Restoring Snapshot

johnboiles · December 13, 2020, 9:38pm

Seeing that HASSOS 5 is stable now, I endeavored to upgrade from a supervised install on Rasbpian to HASSOS 5 64-bit on my Raspberry Pi 4. However when I flash my SSD and try to upload my snapshot I get an HTTP status code 413: Request Entity Too Large with response Maximum request body size 1073741824 exceeded, actual body size 1073743456. So I guess HASSOS can’t take snapshots more than 1gb? Mine is 3.58gb. Bummer there’s no warning about that when downloading a snapshot! I’m going to try to work around this (perhaps complete HA setup, ssh the backup to the pi, then restore? Or maybe try to strip some things out of my snapshot?) and I’ll update here with my progress.

anon43302295 · December 13, 2020, 10:15pm

I would suggest reporting this as a bug. Anyone who is using addons for long term data storage on their system’s full backup is likely to be over a gig. Especially with the new ‘media’ folder.

Although, I just checked my weekly backup and they’re significantly smaller, but I don’t use either feature I just talked about

johnboiles · December 13, 2020, 10:41pm

Ok this wasn’t as bad as I thought it would be originally. The supervisor can handle large snapshots just fine, just not over HTTP. Here’s what I did to work around:

Complete setup as normal
Install the Samba add on (and set a password in Configuration)
Connect to the backup share via Samba
Upload my snapshot
Go to the Supervisor -> Snapshots menu, snapshot should show up
Restore snapshot

I dug into the snapshot a bit and it’s definitely my MariaDB that’s huge. For some reason my DB didn’t restore properly anyways with the snapshot restore – still investigating why that is.

johnboiles · December 13, 2020, 10:43pm

Eek my lovelace setup didn’t make it either (is that in the database?)

johnboiles · December 13, 2020, 10:51pm

looks like it’s a known issue that MariaDB snapshots do not work

github.com/home-assistant/addons

MariaDB does not recover from HASS.io backup

opened 08:19AM - 23 Aug 19 UTC

closed 08:10AM - 21 Feb 20 UTC

ghost

bug Help wanted

*@Spirituss commented on Aug 22, 2019, 8:19 PM UTC:* **Home Assistant release w…ith the issue:** Home Assistant 0.97.2 **Last working Home Assistant release (if known):** Unknown (but it definitely worked earlier). **Operating environment (Hass.io/Docker/Windows/etc.):** Hass.io/Docker/Raspbian Buster **Component/platform:** MariaDB add-on used as record/history component. **Description of problem:** After recovery from Hass.io snapshot MariaDB doesn't work any more. The only way to force it to work is to uninstall the add-on and install it again with the same settings. Of course, in this case you lose your DB and history. **Problem-relevant `configuration.yaml` entries and (fill out even if it seems unimportant):** ``` recorder: db_url: mysql://hass:[email protected]/homeassistant?charset=utf8 purge_interval: 7 purge_keep_days: 7 ``` **Traceback (if applicable):** **Additional information:** It works fine on one of earlier version of hass.io. *This issue was moved by [frenck](https://github.com/frenck) from [home-assistant/home-assistant#26152](https://github.com/home-assistant/home-assistant/issues/26152).*

github.com/home-assistant/addons

MariaDB does not recover from HASS.io backup

opened 10:51AM - 25 May 20 UTC

closed 07:44PM - 08 Jun 21 UTC

Spirituss

add-on: mariadb

**Home Assistant release with the issue:** Home Assistant 0.110.2 **Last w…orking Home Assistant release (if known):** Unknown (but it definitely worked earlier). **Operating environment (Hass.io/Docker/Windows/etc.):** Hass.io/Docker/Supervised **Component/platform:** MariaDB add-on used as record/history component. **Description of problem:** After recovery from Hass.io snapshot MariaDB doesn't work any more. The only way to force it to work is to uninstall the add-on and install it again with the same settings. Of course, in this case you lose your DB and history. **Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):** ``` recorder: db_url: mysql://hass:[email protected]/homeassistant?charset=utf8 purge_interval: 7 purge_keep_days: 7 ``` **Traceback (if applicable):** **Additional information:** It worked fine on one of earlier version of hass.io. There are other issues containing relevant information that were closed without a solution: https://github.com/home-assistant/core/issues/26152 https://github.com/home-assistant/hassio-addons/issues/667

anon43302295 · December 13, 2020, 10:59pm

Yeah, but you should be able to upload it during onboarding - that’s the point of the upload button.

Your lovelace setup isn’t stored in the database, it’s in the .storage directory. The issue with mariadb should only have affected your history.

johnboiles · December 13, 2020, 11:00pm

Yeah, but you should be able to upload it during onboarding - that’s the point of the upload button.

100% agree.

Your lovelace setup isn’t stored in the database, it’s in the .storage directory.

Yeah, strangely, once I reset my MariaDB and blew away my backup, my Lovelace worked again

So my snapshot was too big because of my MariaDB database. And MariaDB snapshots don’t even work in the first place

chris669 · March 15, 2021, 6:24pm

I also have 1.9Gb snapshot how can this be? Just database???

demeulemeesterdries · March 22, 2021, 9:56am

Just created a backup and tried to upload it back using the lovelace interface. I get the “Uploaded snapshot is too large” error.
Backup is only +/-30MB…

Copied over the backup using scp and all went fine… So the backup file itself is valid.

Used versions:

inverse.chi · December 30, 2021, 4:12pm

You can inspect the snapshot (using an archive manager) and see what’s causing it to bloat. E.g. in my case it’s the database.

mgim · September 20, 2024, 7:26am

I am no longer on local network. I have access to HA via Duckdns and NGINX and I am trying to restore a 200MB backup. The error message “Uploaded backup is too large” is quite frustrating. Any clue how to solve that? Samba can only be used in local network, right?