The Linux Release Upgrade
One Linux server moved up to its next operating-system release in place — Ubuntu 22.04 to 24.04, Debian 11 to 12, Rocky or AlmaLinux 8 to 9 — inside a window you set, with a whole-machine snapshot taken first so there is always a way back.
An operating system a release behind runs out of road. Security updates thin out, new software stops installing, and sooner or later a vendor or an auditor asks what you are running. The upgrade keeps getting postponed because it is the one maintenance job that can leave a server that does not come back.
We move one server up one release in place, inside a window you choose, then check it back against how it looked before we started: the same services running and the same ports answering, on the new release. A whole-machine snapshot goes in first, so if the run goes badly one restore puts you back exactly where you were. Our admins make these hops on Ubuntu, Debian, Rocky and AlmaLinux most months, and they know which ones bite.
A newer release also brings newer PHP, Python, OpenSSL and database versions underneath whatever you run on top. You get a line-by-line record of which of those moved, so your testing is targeted instead of hopeful. If your own application turns out to dislike the new versions, the snapshot is still there, and working through the breakage with you is The Server Admin Day.
What's included
One server moved up one release in place, inside a maintenance window you set — Ubuntu, Debian, RHEL, Rocky Linux or AlmaLinux
A whole-machine snapshot taken and confirmed before the first package moves, so one restore puts you back where you started
The server checked back against how it looked beforehand: every service that was running is running again, every port answering, no new failures
A before-and-after record of the PHP, Python, OpenSSL and database versions your applications now sit on, so you know what to test first
Your own configuration files kept exactly as you wrote them, with anything the new release wanted to change listed for you rather than overwritten
Third-party repositories inventoried and taken out of the way for the run, then pointed at the new release where the vendor publishes one
A plain-English handover of what changed, what the new release no longer carries, and the one line that rolls the whole thing back
Before you order
Have these ready so we can start the moment you order. The delivery clock only runs while we have them.
SSH access with sudo or root to the server. It must be a normal VM or physical machine, not a container
A whole-machine snapshot you have confirmed you can restore, or access to your hypervisor or cloud panel so we can take one
Console access (cloud console, IPMI or KVM), or your written acceptance that without it the snapshot is the only way back
A maintenance window of at least four hours, when the server can go offline, and a way to reach you during it
An active Red Hat subscription, if the server runs RHEL
How it works
Book it — pay the fixed price and tell us the target environment. No scoping call first.
We deliver — an experienced specialist runs our standard workflow for this exact task. You can watch progress and message them in the portal.
Hand-off — you get the deliverables, the documentation, a rollback snapshot, and a walkthrough if you want one.
Who does it
A salaried Support Resort specialist with more than ten years in the field, working from a runbook we've been refining since 2003 — supervised by senior management, never a marketplace contractor. You'll see who is assigned and can message them about this task directly in your portal.
FAQ
Ask about this task
Our assistant knows the scope document and runbook behind this service. Ask what's covered, what isn't, or whether it's the right task for your situation.
Answers come from our published scope documents. Prefer a person? Switch to the "Email us" tab — a senior manager replies personally, usually the same weekday.
Related services
The Linux Patching Plan
Up to 10 Linux VMs patched every month in a weekday window you choose. Each one is snapshotted first, rebooted and checked, and two urgent runs a month cover the fixes that cannot wait.
The Web Server Migration
Up to five sites moved to a new server with their configuration and databases, proven working there before a single visitor is sent across — and the old server left untouched, so going back is one DNS change.
The Server Admin Day
A senior system administrator works a full day on your server backlog, from the patch level nobody has checked to the backup nobody has restore-tested. Book one day or a run of dates, and each day ends with a written account of every hour.
The Linux Server Hardening
One production Linux server closed off at the operating-system level to the break-in routes attackers rely on — with before-and-after evidence of every change we make.