#share is backed up during full backups

1 messages ยท Page 1 of 1 (latest)

silver prism
#

thanks again for giving me some pointers. This is the closest I've been to reviving the instance! Now the add-ons are failing to start. Their configuration is there, but I'm getting errors like

#
Image zigbee2mqtt/zigbee2mqtt-amd64:1.18.1-1 does not exist for addon_7ad98f9c_zigbee2mqtt
young pike
#

If this is post restore, reboot the whole host (the VM) from the hardware page in settings

#

3 dots in the upper right corner

silver prism
#

It's my own custom "restore". Pretty much copying everything from the old VM's supervisor/homeassistant directory. I did notice that 2 files had been corrupted in the .storage folder

young pike
#

Add-ons won't be a part of that kind of restore

silver prism
#

core.config_entries and another one.

#

I also copied all the configs files from hassos-data/supervisor

#

then I copied addons/core addons/data

#

I'm guessing that one of the config json file is pointing to different versions of some addons I have installed

#

I'll do some more analysis, but it's promising... I did put a lot of effort into this and would hate to loose it (lots of automations, connections to influxdb, many esphome devices, lots of scenes...)

young pike
#

ESPHome devices should just show up to be added, automations and scenes are part of /config if all hidden directories are included. It's the addon stuff that will be missing mostly

silver prism
#

so when the system complains about zigbee2mqtt/zigbee2mqtt-amd64:1.18.1-1 that's because it's reading some sort of manifest?

#

because as far as I can tell, I did restore that version of zigbee2mqtt's data under supervisor/addons/data

#

but I guess images are loaded from somewhere else

young pike
#

Images are downloaded, they run as containers.

#

They aren't backed up but downloaded again

#

The data for them is backed up, yeah

#

It's like having the CD case and no CD

#

Well, not a great analogy but...

silver prism
#

I'm somewhat familiar with docker at a high level (I use a custom docker image for our build of Squeezelite-esp32 on GitHub).

#

it's the concept of overlays and stuff which I haven't quite grasped in HomeAssistant

young pike
#

I apologize further then ๐Ÿคฃ

silver prism
#

don't

#

I may even "think" I "Know" and yet not really know

#

so better have all the info and filter out what's not needed ๐Ÿ˜„

#

this is the first time I have to dig that deep into Home Assistant

#

and this isn't the type of architecture I'm used to

#

and what happened just proved it

#

I tried copying the entire docker folder from hassos-data from the old to the new

#

and guess what

#

I'm back to my original problem

#

a crapload of errors from containerd

#

so I guess I need to roll back to when I "only had" this error

#
Image zigbee2mqtt/zigbee2mqtt-amd64:1.18.1-1 does not exist for addon_7ad98f9c_zigbee2mqtt
#

unless you have a magic wand of some sort ๐Ÿ˜„

#

I'm thinking that this error is probably easier to resolve, perhaps by reinstalling the add-on. with luck, the new addon will keep the existing config files

#

I hope I'm not abusing this sub thread

#

it's my turn to apologize :S

silver prism
#

@young pike the restore was a success, especially after running supervisor update, core update amongst others.

#

I had to uninstall mariaDB and reinstall it, though. Is there any way I can recover my historical data... somehow ?

#

knowing I still have a backup of the original VDI