The backup service is now built by automation, not by hand

The new backup service was stood up by hand during the hardware move, which was the right call at the time but left it as the only machine outside automated configuration management. Anything set up by hand drifts, and a rebuild would have meant remembering the steps.

It now has its own automation covering the same ground the other machines already get: software sources, time synchronisation, monitoring and backup agents, login personalisation, and the alerting that was added alongside it. Re-running it changes nothing, which is the test that it actually matches what is running.

This also puts the machine on the correct software source, clearing the licence warning it displayed on every login, and adds a safeguard to the shared automation so that the general-purpose server role can no longer run against - and reboot - the backup service by mistake.