Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
Upgrade a VPS as an attended maintenance change, not as a routine package update. Confirm that your current release has a supported path to the target, patch it fully, back up data independently of a provider snapshot, and make sure a serial, web, or rescue console works before you begin. Run the distribution’s upgrader inside tmux or screen, keep configuration prompts under supervision, reboot when instructed, and verify the operating system, networking, services, and application before declaring success. Ubuntu Server and cloud images use do-release-upgrade; Debian follows the current stable-release notes; RHEL major transitions use Leapp; and SUSE Linux Enterprise Server uses its documented migration or distribution-upgrade workflow.
What is the safest way to upgrade a Linux distribution on a VPS?
The safest method is a staged, reversible change with two access routes and two recovery layers. First establish the supported release path and a maintenance window. Then capture a provider snapshot of the boot disk and separate copies of databases, application files, secrets, configuration, and attached-volume data. Start a persistent terminal session, verify alternate console access, run the distribution-supported upgrader, and stay available for every package and configuration decision. After the reboot, test the operating system and the real application path before removing the snapshot.
Free tools Windows power users keep installed
One-click scans. No signup required.
As an Amazon Associate I earn from qualifying purchases.
A distribution upgrade replaces a large part of the operating system. It can stop services, change a kernel, rewrite network or SSH configuration, disable third-party repositories, and require a reboot. The download phase is not the finish line: Canonical’s Ubuntu guidance says the system is not upgraded until the requested reboot occurs.
Should you upgrade in place or move to a replacement VPS?
In-place upgrades preserve the existing machine and usually avoid a full application migration, but they expose you to package and configuration drift accumulated over time. A replacement VPS lets you build and test the target release separately, then switch traffic, but it requires a migration plan and a way to synchronize data.
Popular on Amazon
- Read Before You Buy — No Video Output: These adapters support charging and USB 2.0 data transfer, but cannot transmit video signals. Except for standard USB webcams (which use USB data only), they are not compatible with HDMI/DisplayPort cables, video-capable USB-C hubs, or docking stations with video output.
- Convert USB-A Ports to USB-C: Designed to connect USB-C earphones, cables, flash drives, card readers, and other USB-C accessories to standard USB-A ports. Plug-and-play with no drivers or software required.
- Aluminum Alloy Housing: Built with a sturdy aluminum alloy shell that aids in heat dissipation and protects against daily wear and scratches. Designed to maintain a stable and secure connection.
- Compact & Travel-Friendly: The ultra-compact design allows the adapter to stay plugged into your device without blocking adjacent ports or adding bulk, reducing wear and tear on your original USB ports.
- 12-Month Warranty: Backed by a 12-month manufacturer warranty for peace of mind. Designed to meet strict quality control standards for reliable everyday performance.
| Decision factor | In-place upgrade | Replacement VPS |
|---|---|---|
| Release support | Must follow the distribution’s exact sequential path. | Can start directly from a supported image, subject to application compatibility. |
| Downtime | Includes package replacement and at least one reboot; service interruptions can occur earlier. | Can reduce cutover downtime if the new instance is prepared in advance. |
| Recovery | Depends on a boot-disk snapshot, console access, and independent data backups. | Old VPS can remain available while the replacement is validated. |
| Configuration drift | Old repositories, local edits, and obsolete packages remain part of the change. | Provides a clean baseline, but every required setting must be recreated. |
| Attached volumes | Remain in place, but still need a backup and mount verification. | Must be attached or restored and checked on the new machine. |
| Testing | Testing happens on the production system after the reboot. | Supports a clone or staging test before DNS or load-balancer cutover. |
| Provider limits | Check snapshot coverage, regional quotas, and console availability. | Check image availability, IP or volume limits, and the cost of running both instances. |
Choose a replacement when the provider offers an easy clone and the application can be replicated, when downtime is tightly constrained, or when the existing installation has substantial unmanaged changes. An in-place change is reasonable when the provider documents the path, the system is well maintained, and you have tested restoration.
Recommended Free Tools
What should you record before changing the VPS?
Create a short inventory that another administrator could use to reconstruct the machine. Store it outside the VPS so it remains available if the boot disk will not start.
- Current distribution, codename, architecture, kernel, and package-manager state from
/etc/os-releaseand the distribution’s release command. - Enabled repositories, PPAs or vendor repositories, pinned packages, held packages, and installed package selections.
- Running and enabled services, listening ports, system users, SSH keys, firewall rules, DNS settings, routes, mounts, swap, scheduled jobs, timers, and the provider guest agent.
- Application versions, runtime dependencies, certificates, queues, workers, database endpoints, external integrations, and health-check URLs.
- Locations of attached volumes and any data that is generated outside the boot disk.
Read the target release notes and your provider’s image documentation before scheduling the change. Ubuntu’s current guidance permits an LTS-to-LTS upgrade only to the next LTS; if several LTS releases separate your source and target, plan a separate upgrade and validation for each hop. Canonical’s 2026 documentation lists five years of standard support for an Ubuntu LTS release and nine months for an interim release, so record the exact edition and support status rather than assuming every Ubuntu image has the same lifetime.
How do you back up a VPS before a distro upgrade?
Use a provider boot-disk snapshot for rapid machine-level recovery, then create independent, restorable copies of everything the snapshot may omit or capture inconsistently. Google Cloud’s upgrade guidance calls a boot-disk snapshot the primary recovery mechanism for an in-place upgrade, but a snapshot alone does not prove that a database or continuous application will restart cleanly.
Take the provider snapshot
- Stop or quiesce write-heavy workloads if your application’s backup procedure requires it.
- In the provider console, snapshot the boot disk immediately before the upgrade. Confirm the snapshot is complete and record its name, timestamp, region, encryption settings, and retention policy.
- Verify the provider’s documented restore path: creating a replacement VPS from the snapshot, attaching the restored disk, or reverting the original disk. Do not wait until an outage to discover that a snapshot cannot be restored across regions or to a different machine type.
Create independent copies
- Export databases with their native dump or backup mechanism and record the dump format and restore command.
- Back up
/etc, package state, service definitions, firewall configuration, certificates, application code, uploads, and secrets. Debian specifically identifies/etc,/var/lib/dpkg,/var/lib/apt/extended_states, anddpkg --get-selections '*'as valuable recovery information. - Back up attached volumes separately. A boot-disk image may not include them, and a volume snapshot taken during writes may not be application-consistent.
- Keep an off-provider copy for important data. Protect credentials and encryption keys independently of the VPS account.
Rehearse restoration
When the service matters, restore to a separate instance before the maintenance window. Confirm that the restored machine boots, mounts volumes, resolves DNS, accepts credentials, starts services, and serves a real application request. Record the usable recovery point and elapsed recovery time; these are operational facts, not guarantees supplied by a snapshot label.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteAlso popular on Amazon
- 5-in-1 USB-C Hub: Experience comprehensive connectivity featuring a Power Delivery input, two USB-A 2.0 ports, a USB-A 3.0 port, and an HDMI port. (Note: The USB-C power delivery input port is only for connecting an external wall charger to power your laptop and cannot power peripheral devices.)
- 90W Pass-Through Charging: Achieve optimal charging with 90W pass-through power to your laptop, supported by a total input of 100W, with the hub reserving 10W for operational efficiency. (Note: Wall charger not included.)
- Quick Data Transfers: Accelerate your productivity with rapid data transfers using a high-speed 5Gbps USB 3.0 port and two 480Mbps USB 2.0 ports.
- 4K HDMI Display: Enhance your visual experience with a hub capable of delivering 4K resolution at 30Hz in both mirror and extend modes. Please note that this hub is compatible with MacBook (macOS 12 and newer), Windows 10 and 11, ChromeOS, and laptops equipped with DP Alt Mode and Power Delivery. Note: This device is not compatible with Linux.
- What You Get: Anker USB-C Hub (5-in-1, 4K HDMI), welcome guide, 18-month warranty, and our friendly customer service.
How do you prevent an SSH session from killing the upgrade?
Run the upgrade inside tmux or screen, and arrange a second access route before launching it. A dropped SSH connection should not terminate the package process, while a kernel, firewall, or network failure after reboot may make SSH unavailable altogether.
- Open the provider’s serial console, web console, or rescue environment and authenticate before the change. Keep its URL or access instructions with the change record.
- Connect over SSH and start a persistent session, for example
tmux new -s distro-upgrade. Detach withCtrl-bfollowed byd; reconnect later withtmux attach -t distro-upgrade. - Test that a second SSH connection works and that your administrative account has a working key and
sudoaccess. - Notify users and monitoring contacts of the maintenance window. Package scripts can stop services before the reboot, and an unattended configuration prompt can extend the outage.
- Keep the console open while the upgrader runs. Do not close the only terminal after the download phase appears complete.
How do I upgrade Ubuntu Server or a cloud image?
Use Canonical’s supported do-release-upgrade workflow, one supported release hop at a time. Do not attempt to skip an LTS release, and do not start until the current release is fully patched and any required pre-upgrade reboot has completed.
- Confirm the target. Read the target release notes and verify that the installed LTS can move directly to that next LTS. Check the provider’s supported Ubuntu images and any guest-agent requirements.
- Patch the current release. Run
sudo apt update, thensudo apt dist-upgrade -o APT::Get::Always-Include-Phased-Updates=true. Reboot first if Ubuntu reports that a reboot is required, then reconnect throughtmuxorscreen. - Check availability. If you only need to determine whether a distribution upgrade is offered, the Ubuntu man page documents
sudo do-release-upgrade --check-dist-upgrade-only. - Install the upgrader when needed. On a minimal image, install it with
sudo apt install update-manager-core. - Launch from the persistent session. Run
sudo do-release-upgrade. Canonical recommends this command for Server edition and cloud images rather than manually changing repositories. - Read the pre-upgrade summary. Review proposed removals, additions, downloads, disabled repositories, and required disk space. Stop if an essential package, provider agent, or application dependency is unexpectedly scheduled for removal.
- Resolve configuration files deliberately. Compare the locally modified file with the package maintainer’s version. Keep local settings only when they are still valid for the target release; install the maintainer version when the old file contains obsolete syntax, then reapply the required local values carefully.
- Remain available through configuration and cleanup. Answer prompts, watch for errors, and wait for the upgrader to request a reboot. Finishing downloads does not mean the operating system has been converted.
- Reboot and reconnect. Use the normal SSH path and the alternate console if necessary, then complete the verification sequence below.
Third-party repositories and PPAs are a common source of Ubuntu upgrade failures. Disable them or confirm target-release compatibility before starting, and re-enable each one only after its maintainer publishes packages for the new release.
Can I upgrade Debian in place?
Yes, but Debian upgrades should follow the current stable-release notes exactly and proceed between consecutive releases. The repository codename changes, package transition order, and known issues vary by release, so a generic command sequence is not a substitute for the notes for your target.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →- Read the target Debian release notes and provider instructions. Make the full backup Debian recommends, including data and configuration that cannot be recreated.
- Bring the current release to its latest point update and remove or disable third-party repositories that do not publish packages for the target codename.
- In the repository definitions, change only the current codename to the next release codename. Keep the change under version control or save a copy of the original files.
- Run
sudo apt update, thensudo apt upgrade --without-new-pkgsto perform the initial transition. - Run
sudo apt full-upgradeand read removals, replacements, and configuration prompts. Stop if essential provider integration packages are being removed without a documented replacement. - Verify the provider or guest agent, mounts, networking, SSH, and application services before rebooting.
- Reboot from the persistent console session and perform post-upgrade checks. Debian warns that services may be stopped while packages are replaced and recommends
screenortmuxplus an alternate serial or local console for remote upgrades.
Google Cloud publishes a Debian workflow using these stages, but its integration packages and repository layout are provider-specific. Do not copy that sequence mechanically to another VPS provider without checking the provider agent and the current Debian notes.
Also popular on Amazon
- Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
- Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
- Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
- Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
- What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.
How do RHEL-family systems and SLES differ?
RHEL major-version transitions
For a RHEL major upgrade, use Leapp rather than treating the change as an ordinary package update. Google Cloud’s documented flow is to verify subscription and repository connectivity, install the supported Leapp packages, run a pre-upgrade assessment, clear every inhibitor, then launch the transition.
- Confirm that the subscription, enabled repositories, provider image, and target major version are supported.
- Install the Leapp packages specified for the source and target versions.
- Run
sudo leapp preupgrade. - Read
/var/log/leapp/leapp-report.txtand resolve every inhibitor. Do not proceed merely because warnings are present; an inhibitor means the transition is blocked until its condition is corrected. - Run
sudo leapp upgrade, remain connected through the alternate console, and reboot when instructed so the upgrade environment can complete the transition.
SUSE Linux Enterprise Server
Use zypper patch for current updates, but use the documented service-pack migration or distribution-upgrade procedure for a release transition. Depending on the SLES version and provider, that may be zypper migration or a documented zypper dup workflow. Confirm the exact repositories, service pack, reboot requirements, and provider procedure before changing them.
How should you handle configuration-file prompts?
Prompts are decisions about behavior, not interruptions to click through. A maintainer version may contain new directives required by the target release, while the local version may contain provider networking, SSH hardening, database paths, or application settings you still need.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →- Record the path and package that owns the file.
- Compare the old and new versions, preserving a copy of both outside the VPS if possible.
- Check syntax with the service’s validation command before restarting it.
- Keep only settings that are still supported; remove obsolete directives rather than carrying them forward blindly.
- Restart one affected service at a time and inspect its status and logs before continuing.
For SSH, keep an existing session open until a new connection succeeds. For network configuration, verify the provider’s expected interface name, routes, DNS, and firewall before closing the console.
What happens if the VPS reboots halfway through?
A reboot can be normal when the upgrader explicitly requests it, but an unexpected reboot or a boot that never reaches multi-user mode requires controlled diagnosis. Do not repeatedly reboot without checking the console and logs.
Also popular on Amazon
- Dual Converters, Infinite Potential：Includes 2× USB C male to USB A female adapters and 2× USB A male to USB C female adapters. Perfect for a wide range of uses—tablets with Bluetooth keyboards, expand USB ports on macbook, and more. Two different converters for all your daily needs
- Next-Level 10Gbps & 3A Charging: No more slow 480Mbps, this usb to usb c adapter has a transfer speed of up to 10Gbps, allowing you to do more transferring in less time. This usb adapter fits both USB A and USB C charger, supporting up to 3A fast charging
- Upgraded Exquisite Craftsmanship: With an aluminum alloy housing and metal connector, the usbc to usb adapter is extremely durable and sturdy. Rigorously tested to withstand more than 10,000 times of plugging and unplugging, ensuring long-lasting performance
- Widely Compatible: Transform any USB-C port into a USB-A port and USB-A port into a USB-C port, and connect up a wide range of USB-C(including MacBook, iPad Pro/Air/Mini, iPhone models with USB C ports, Samsung Galaxy series, and Google Pixel series. ) and USB A devices(including external hard drives, phones, mice, printers, and more)
- Please Note: To reach 10Gbps speed, keep the cable under 3.3 ft. For USB A Male to USB C adapters, try flipping the USB C connector. USB C Male to USB A adapters support bidirectional 10Gbps transfer within 3.3 ft
If the machine boots but SSH is unavailable
- Open the provider serial or web console and log in locally.
- Check the address and route with
ip addrandip route; check name resolution withresolvectl statuswhere available. - Inspect
systemctl --failed,journalctl -b -p err..alert, and the package-manager log. - Verify that the SSH service is enabled, its configuration parses, the firewall allows the intended port, and the provider guest agent is running.
- Correct one issue, restart the affected service, and test a new SSH connection before making further changes.
If the system drops into emergency mode
Read the console message and boot journal. A stale filesystem identifier, missing attached volume, or invalid mount option can block boot after a release change. Correct the specific entry, use a rescue environment if the root filesystem cannot be mounted, and avoid deleting data to make the system boot faster.
If package configuration was interrupted
From the console, let the package manager finish its pending configuration using the command recommended by the distribution’s release notes. On Debian-family systems, inspect dpkg --audit and package-manager output before attempting another full upgrade. On RHEL-family systems, follow Leapp’s reported state rather than installing unrelated packages.
If recovery is faster than repair
Stop the VPS, create a replacement from the pre-upgrade snapshot, and attach or restore data volumes according to the provider’s procedure. Keep the failed disk intact for investigation. If the snapshot cannot provide application-consistent data, restore the independent database and application backups instead.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How do you verify the VPS after the reboot?
Verify in an order that limits the blast radius: operating-system identity first, then package state, infrastructure, services, application behavior, and monitoring.
- Confirm identity. Check
cat /etc/os-release, the codename, architecture, anduname -r. Confirm that the running kernel is the expected target-release kernel. - Check package completion. Review package-manager logs, held or broken packages, and
dpkg --auditon Debian-family systems. Confirm that no requested upgrade step remains unfinished. - Check services. Run
systemctl --failed, inspect every expected service withsystemctl status, and confirm enabled services remain enabled. - Check storage. Verify disks, filesystem capacity in
/,/var, and/boot, swap, attached volumes, mount options, and inode availability. Test mounts without writing destructive data. - Check networking and access. Verify interfaces, routes, DNS, time synchronization, firewall policy, SSH keys, listening ports, and the provider guest agent. Test both normal SSH and the alternate console.
- Exercise the application. Use its real health endpoint or client path. Confirm database connections, queues, workers, certificates, scheduled jobs, and external integrations rather than relying only on a process being “active.”
- Check operations. Confirm monitoring, log shipping, alerting, scheduled backups, and backup readability. Ensure rollback instructions still match the provider console and current disk identifiers.
Keep the pre-upgrade snapshot until the observation window passes and the independent backups have been confirmed. The length of that window should match the application’s normal failure-detection cycle and the time needed to restore from backup, not an arbitrary number of hours.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallAlso popular on Amazon
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
How do you roll back a failed Linux distro upgrade?
Rollback is a recovery operation, not an automatic inverse upgrade. Choose between restoring the provider image and rebuilding from independent data according to what failed and what the snapshot contains.
- Declare the incident and stop application writes if doing so protects data consistency.
- Use the alternate console to determine whether the failure is a service, mount, network, package, or boot problem.
- If the boot disk is damaged or repair would exceed the outage budget, create a replacement VPS from the pre-upgrade snapshot or restore that snapshot to a new disk.
- Attach the correct data volumes, or restore database and application data from their independent copies. Check ownership, permissions, credentials, and encryption keys.
- Rebuild networking, firewall rules, DNS, certificates, scheduled jobs, workers, and monitoring. Do not assume a restored image has the same interface name or provider-agent state.
- Run the same application and operational checks used for the forward upgrade, then redirect traffic only after the real health path succeeds.
- Preserve the failed disk and logs until the incident is understood. Record the actual recovery point and elapsed recovery time for the next maintenance plan.
Provider-native backups, database-native dumps, attached-volume backups, and off-provider copies solve different failure modes. Services that support continuous streaming or other always-on workloads need an explicit recovery-point and recovery-time plan; a snapshot label alone does not establish that the workload will restart cleanly.
What mistakes most often turn an upgrade into an outage?
- Skipping a release hop, especially an Ubuntu LTS hop, because the target image looks newer.
- Starting with an unpatched source release or without the reboot it requested.
- Leaving incompatible PPAs or third-party repositories enabled.
- Relying on a snapshot without exporting databases, secrets, and attached-volume data.
- Running over a plain SSH shell instead of
tmuxorscreen. - Closing the console after downloads finish, before package configuration and cleanup complete.
- Accepting every maintainer-file prompt without reviewing provider networking, SSH, and application settings.
- Rebooting repeatedly without reading console output and boot logs.
- Deleting the snapshot immediately after SSH returns, before services, backups, and monitoring have been observed.
Frequently Asked Questions
How long should I keep the pre-upgrade snapshot?
Keep it through the period in which delayed failures would normally appear for your workload, and until an independent backup has been restored or otherwise verified. A stateless web node may need a shorter window than a database or scheduled batch system; the correct duration follows your recovery procedure, not a universal timer.
Can I automate a distribution upgrade with cloud-init or a scheduled job?
Automation can prepare inventories, snapshots, notifications, and health checks, but the release transition itself is interactive on many systems. Configuration prompts, inhibitors, and provider-agent changes require an administrator who can stop the process and use the alternate console.
Should I disable monitoring during the maintenance window?
Do not silence all monitoring. Suppress only alerts that are expected during the declared window, while retaining console, host, disk, boot, and backup alerts so an unexpected failure is visible. Restore normal alerting before the application is returned to service.
Is a cloned test VPS useful if the production server has no spare capacity?
Yes, when the provider can clone the boot disk or create a temporary instance. A clone lets you discover repository, kernel, and application incompatibilities without risking production, but it must use representative attached volumes and configuration or the test can miss the failure you care about.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
