I fully intend to write a full blog-post as a follow-up to my [previous post]({{< ref "/posts/my-first-post" >}}) at some point, detailing some of the quirks of this setup and issues that I ran into - but I just got a timely reminder of the importance of checking backups, and wanted to pass it on to you.
<!--more-->
I have a few Raspberries Pi on my home network. One is running [pi-hole](https://pi-hole.net/) for network-wide ad blocking, one hosts the [Home Assistant Operating System](https://www.home-assistant.io/), one is a [Kodi](https://kodi.tv/)-box, and another is for "everything else" - [Jellyfin](https://jellyfin.org/) as a media server, [Prometheus](https://prometheus.io/) and [Grafana](https://grafana.com/) for monitoring, and anything else that takes my fancy. In keeping with my enthusiasm for Infrastructure As Code, I made sure to note down all the installation instructions I'd used [here](https://github.com/scubbo/pi-tools/tree/main/scripts-on-pi), but I'd never been prompted to actually use it. Recently, however, the "misc" Pi's performance has been gradually degrading (I suspect, but have no proof of this, that it's because of the patchwork of conflicting Python package versions I've installed. As [Matthew Duggan says](https://matduggan.com/mistakes/) - "_Nobody knows how to correctly install and package Python apps_"), and I wanted to make a fresh install to get a clearer view of the situation.
Thankfully, the install scripts worked nearly flawlessly. There were a few hiccups to work around and [improvements to be made](https://github.com/scubbo/pi-tools/commit/3d9a0c939791a13b95f28e0ee07942547ba981ad), but broadly speaking, the transfer of functionality to a new install was a success.
