Moved my install base to an Optiplex 3000 Thin Client and oh boy what a disaster it was.
Got some errors saying the node I was moving to (10.0.0.2) had a link ID of 10.0.0.4. Faffed around in corosync settings, fixed it (or so I thought), ended up making the actual IP 10.0.0.4 and then the link ID changed to 10.0.0.2! WTF? This was causing cluster issues so my new node (Optiplex) couldn't join.
Thought let me rather just nuke the cluster and start over. The GUI doesn't support this but you can do this via the CLI. Did the deed, rebooted the node and lo and behold, no more cluster. Also, no more VM's or LXC's...all were MIA.
Scrounged through the folders and found
references to my missing LXC's and VM's, but the actual stuff was gone. But at least the cluster was destroyed. I then created another cluster on the Optiplex, and joined the old node to it which worked. I then restored all my VM's and LXC's from my 3AM backup, and migrated them to the new node. I believe there is a way to restore backups straight to the other node but it also involved some CLI faffery and I didn't want to FAFO more than I already have.
I think from installing PVE on the Optiplex to having all my services up took around 2.5 hours. One caveat was that as I moved Unifi from a system running an 8500T to one running an N5105, MongoDB wouldn't start as the N5105 is missing AVX instructions. It took another half an hour of messing about with previous versions but eventually found that Mongo 4.2 worked, but it did nuke my Unifi settings. Thankfully, I had backups of these as well and all was right in the world
View attachment 1806642