And a sooner-than-expected software update, or rather; a VM update.
Today I migrated the three remaining VMs from my office node to my main Proxmox host at home. All three VMs belong together: a PostgreSQL database, a Python development machine, and an Nginx reverse proxy.
As I had never migrated VMs before, it sounded like a daunting task.
Spoiler alert: it was as easy as it gets.
Basically:
- Stop the VMs
- Back up the VMs using a single CLI command, although I suspect it would have worked via the Proxmox web interface as well
- Copy the files from one machine to the other
- Import them manually, without starting them
- Start them and update the network configuration
- Add the VMs to the backup scheduler
And done!
The Proxmox host at my office is now completely empty, and I can move the hardware to another case and reinstall Proxmox on it. The new name of the machine will be Gnosis, again taken from The Matrix franchise.
I also made a crucial change to the backup strategy. Previously, I only backed up a specific set of VMs.
The reason; I wanted to exclude one from the list. And yes, you guessed it: all newer VMs and containers did not have a backup strategy yet…
OOPS!
I have set it up properly now. All new VMs are automatically backed up, unless I explicitly exclude them from the set.
If I keep this up, I’ll end up as a battle-seasoned sysadmin 😛
Brain out!