Looking for some guidance on best next steps after an SD card failure. Here’s where we’re at;
-RPi4 with 64GB SD card running Debian 11 and HA supervised, box has a couple other docker containers also for add-ons/integrations in HA (Solar/Off Grid stuff - Voltronic, portainer, etc).
SD card in the RPi4 reached max writes and died (I think, eithr way, not writable and broken).
Built up another Debian box (with gui this time, i5 and SSD based and have stood up another supervised HA instance ready to receive.
SD card was imaged, image shrunk, then written back to a 32GB card I had spare.
Old HA box is now running again on the 32GB card, I have taken full backup using HA backup and downloaded it to the new host. I only have a google drive backup from a year ago only, didn’t realise it had stopped working/disappeared and am currently trying to re-add it so I can take a full backup off to google drive but it’s being a bit problematic.
What’s the best next steps to migrate from the old box to the new?
Restore full HA backup then do a save/export of docker and volumes? I’m not sure how to do the docker bits entirely, specifically volumes.
Just do a copy/paste of the HA config folder (and any others?) then do the same for docker/volumes?
There’s a bit too much work to just re-install everything manually on the new box and reconfigure, some of the config was fiddly and took a while (esphome, solar/bms stuff, automations etc etc).
HA and its add-ons data should be included in the backup. Exception here being media like camera images or video , for example, that you would have specified the addon should access.
For your containers that are not an addon or HA look at portainer. Portainer allows container management and has mechanism for volume export and import.
To restore the other containers i would
-create a default of the container using same version/image from dockerhub or wherever
-export volume from old and import to new. I presume your config data is in the volume, but if these were bind mount you should manually copy this and move it over to new server.
-restart container and check
Exporting containers is only helpful if you created a custom docker image. Not exporting does mean you must know ports and other settings for container. With portainer you should be able to look and verify this. Volume export/import is useful however
Have since managed to create a full backup of the old HA box and restore it on the new host which has gotten me 90%of the way there.
My issue now is debian itself will not “see” the BMS I’m trying to connect to via Blutetooth, it can see my other laptop/phone etc and my phone can seethe BMS on Bluetooth without issue.
Any ideas? I’m on bluez 5.66, when I do a scan I note the powered and discoverable status constantly flick back and forth.
My first instinct is to believe that if everything see everything and problem is just single device, it is device issue. Its bluetooth so if its working then it should work. No in between.
