Essential Pre‑Upgrade Checklist for Production Linux Servers

Purpose of a Production Server Upgrade

Keeping the operating system and server‑side software up to date reduces security exposure, fixes bugs, and provides newer tools. Upgrading a live Linux server without preparation can cause data loss, performance degradation, or service interruption.

Pre‑Upgrade Checklist

Create a Verified Backup Back up both the file system and any databases. Typical commands include:

# Backup website files
rsync -avz /var/www/ /backup/www/
# Backup MySQL databases
mysqldump -u root -p --all-databases > /backup/all-databases.sql

Store the backup off‑site (cloud storage, external drive) and verify that the archive can be restored before proceeding.

Check Software Compatibility Identify the versions of critical libraries, runtimes, and CMS components. For example, run:

# Show OS version
lsb_release -a
# List installed packages that may be affected
dpkg -l | grep -E "php|apache|nginx|mysql"

Confirm that the target distribution (e.g., Ubuntu 20.04 LTS) still provides the required packages. Test custom applications in a sandbox if they depend on specific library versions.

Provision a Temporary Server Spin up a separate instance (same OS version as the current production server or the target version). Restore the backup onto this machine and point a test domain or sub‑domain to it. This allows you to verify the restored site works before touching the primary server.

Configure Load Balancing (Optional) If the site receives significant traffic, place a load balancer (e.g., HAProxy, Nginx, or a cloud‑based LB) in front of the two servers. Add both the primary and temporary server IPs to the pool, then direct all traffic to the temporary server while the primary is being upgraded. After a successful upgrade, switch the traffic back and remove the temporary node.

Schedule a Low‑Traffic Window Use analytics (Google Analytics, Matomo, etc.) to identify the period with the fewest visitors. Perform the upgrade during this window to minimise impact.

Upgrade Execution (Typical Ubuntu Example)

# Update current packages
sudo apt update && sudo apt upgrade -y
# Install the upgrade tool (if not present)
sudo apt install update-manager-core
# Start the distribution upgrade
sudo do-release-upgrade

Monitor the upgrade logs ( /var/log/dist-upgrade/) and be prepared to answer prompts about configuration file changes.

Post‑Upgrade Steps

Verify that all services (web server, database, application code) start correctly.

Run functional tests or browse the site to confirm expected behavior.

If a load balancer was used, re‑point traffic to the upgraded primary server and remove the temporary server from the pool.

Retain the backup for at least a few days in case rollback is needed.

Key Takeaways

Proper planning—full backup verification, compatibility checks, a fallback temporary server, optional load‑balancing, and timing the upgrade during low traffic—greatly reduces the risk of data loss and downtime when upgrading production Linux servers.