Restoring Space 15.2 data to 16.1
The upgrade from Space platform 15.2 to 16.1 is one of the worst procedures I’ve seen in quite a while. It is complicated because the underlying CentOS is being upgraded at the same time, so I guess that’s part of the reason, but still, it could be a lot slicker and better tested.
In summary, you have to apply a couple of patches, the second of which backs your 15.2 data up somewhere else – ideally over SCP to a remote server. You then shut down your 15.2 VM, install a fresh 16.1 VM with the same IP addresses, and restore the data to it.
Sounds easy, but the 16.1 installation part can generally only be done by the customer’s VMware admin because it needs console access. So you’ve got to rely on them following lots of instructions quite well.
Recently a customer experienced some kind of failure in the restoration part, leaving me with a fresh installed 16.1, but no data. I SSHed on to the VM and could see the standard menu, but wasn’t offered any option to attempt another restore. After digging around for a while, I found Continue reading



is all available from the API.