PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, 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 minuteSwitching a VPS from Debian to Ubuntu is safest as a rebuild-and-restore migration, not as a conversion of the running Debian installation. Back up and verify your game-server files, worlds, databases, configuration, and secrets off the VPS; confirm you can reach the provider’s recovery console; then install Ubuntu, rebuild the services, restore and test the data, and move traffic only when the new server is ready. Keep the Debian instance available until your rollback window ends.
Need a server to try this on? Antihost offers Linux VPS plans with NVMe storage, full root access and a 14-day free trial.
Can you switch Debian to Ubuntu without reinstalling?
There is no recommended Debian-to-Ubuntu upgrade command for converting a production VPS in place. Ubuntu’s do-release-upgrade is for moving an Ubuntu Server or cloud image between Ubuntu releases; it is not a Debian-to-Ubuntu switch tool.
As an Amazon Associate I earn from qualifying purchases.
Debian and Ubuntu both use APT, but that shared package-management foundation does not make their system packages interchangeable. Package versions, patches, dependencies, repository assumptions, and configuration defaults can differ. Replacing Debian’s APT sources with Ubuntu repositories on a live production system risks leaving a mixture of packages that is difficult to recover or support. A clean Ubuntu installation followed by a selective restore is the more predictable approach, particularly when the VPS has third-party repositories or packages whose compatibility is uncertain.
For a game server, treat the operating system and the game’s persistent data as separate things. The goal is to rebuild the Ubuntu host and its services while preserving the worlds, player or server data, configuration, and other files that actually need to survive. Do not assume the VPS provider’s reinstall process will preserve them.
#1 Best Overall
Choose a migration route before changing the server
The practical choice is between reinstalling the existing VPS and building a replacement. A parallel replacement usually makes rollback clearer for production: Debian stays intact while Ubuntu is configured and tested. A provider-side reinstall may be simpler when the provider offers a suitable Ubuntu image, but the old installation may not remain available. An in-place experiment is the least predictable route and should not be treated as a safe production migration plan.
| Approach | Rollback | Downtime and traffic | Best fit |
|---|---|---|---|
| Build a replacement VPS | Usually clearest: leave Debian available while testing Ubuntu, then switch traffic when ready. | Can reduce the period when the service is unavailable, though final data synchronization and cutover still need planning. | Production servers where keeping a working Debian instance matters. |
| Provider-side reinstall | Depends on whether the provider can restore the prior instance or snapshot; do not assume the old system remains intact. | The service may be unavailable during reinstall and restoration. | VPS plans with a suitable Ubuntu image and verified backups and recovery access. |
| Attempt an in-place package conversion | Hard to reason about if the package base becomes mixed or the server stops booting. | Failure can interrupt the only running instance. | Not a recommended production route; shared APT tools do not establish package compatibility. |
Before selecting a route, check whether the provider offers a supported Ubuntu Server or cloud image, whether the public IP can be retained, whether attached storage can be mounted on a replacement, and what console, rescue, or serial access is available. Also account for IPv4 and IPv6 addressing, firewall policy, and the Ubuntu release’s support lifecycle. The exact image choices and preservation of IPs or volumes depend on the provider and plan.
Inventory the Debian VPS before you touch it
Write down what the server does and what must be reproduced. A game server may have more than one service behind it: the game process, a web map or control panel, a database, a proxy, monitoring, backups, or scheduled maintenance tasks. Missing one dependency can make the new VPS appear healthy while players cannot connect or important functions remain broken.
- System identity and access: Debian release, hostname, public IPv4 and IPv6 addresses, administrator accounts, SSH keys, and any non-default SSH settings.
- Network and exposure: firewall rules, listening services, game and management ports, DNS records, load-balancer targets, and any provider network controls.
- Game and application data: worlds, saves, uploads, server settings, plugins or mods, allowlists, ban lists, logs that must be retained, and persistent container volumes.
- Supporting services: web servers, databases, queues, container workloads, monitoring, certificates, and externally installed software.
- Automation: cron jobs, systemd timers, service units, startup scripts, backup jobs, and maintenance schedules.
- Storage: mount points, attached volumes, filesystem layout, and any directories outside the obvious application data path.
- Package provenance: APT source files, third-party repositories, and software installed outside the standard Debian repositories.
Package selections and package-state information can help you remember what was installed, but they are not a ready-made Ubuntu installation recipe. Review each package and repository against Ubuntu and the software vendor’s own instructions rather than replaying Debian package state blindly.
Back up the data that must survive
Make backups before reinstalling or changing storage. Keep at least one copy off the VPS; a snapshot stored only within the provider account or on the same VPS should not be your only recovery copy. A backup is useful only if you can retrieve and restore it.
Preserve configuration and system context
Save /etc as a reference, along with service configuration under /usr/local or /opt where applicable. Retain relevant package selections and package state, including /var/lib/dpkg and /var/lib/apt/extended_states, if they will help you reconstruct what the Debian host was doing. These records are recovery aids, not instructions to copy the old operating system wholesale onto Ubuntu.
Free tools Windows power users keep installed
One-click scans. No signup required.
Export databases with their application’s method
Use the database or service’s documented export format and import procedure—for example, an SQL dump or an LDIF export where appropriate. Copying a database’s live storage files without an application-supported method can leave you with data that is unusable on the new host. Preserve any credentials and connection settings needed to restore the service, but store secrets securely rather than leaving them in a public or shared backup location.
Copy game files and persistent application data
Identify the actual data directories for each game server and supporting application. Include worlds and saves, uploaded files, configuration, persistent volumes, and any other state that should remain. Plan to preserve file ownership and permissions when restoring; the Ubuntu host may use different user and group IDs, so check ownership against the account that will run each service instead of assuming old numeric IDs will be correct.
Test the backup before relying on it
Restore a representative selection of files and at least one database export in a safe location or test environment. Confirm that the archive can be read, the expected files are present, and the database import completes. Decide where copies live, how often they are refreshed during the migration, and how restoration will work. For a long-running game world, plan for a final copy or synchronization close to cutover so changes made after the first backup are not lost.
Rank #4
Keep a way back into the VPS
An operating-system reinstall can remove SSH access, alter network configuration, or leave the server unable to boot. Before stopping or reinstalling the VPS, sign in to the provider’s web console, rescue environment, serial terminal, or equivalent out-of-band recovery method and verify that it works for this instance. Do not rely on SSH as your only recovery path when the operation can change the OS or network.
Confirm how to select or restore the intended Ubuntu image, how to reach rescue mode if the install fails, and how to recover the backup if the VPS does not boot normally. If using a replacement VPS, verify console access there too before directing production traffic to it.
Install Ubuntu and rebuild the services
- Select the target image. Choose a supported Ubuntu Server release offered by the provider, or use the provider’s Ubuntu cloud-image option. Check the image and storage choices before confirming an install: installation and partitioning can destroy data on the target VPS.
- Install on a clean target. For a replacement, provision Ubuntu separately and attach or mount only the data needed for restoration. For a provider-side reinstall, proceed only after the off-host backup and recovery route have been verified.
- Recreate access and network policy. Rebuild administrator users and groups, install the intended SSH keys, apply SSH hardening, and restore firewall policy deliberately. Check both IPv4 and IPv6 behavior where the service uses them.
- Install the software. Recreate game-server and supporting services using Ubuntu repositories or the relevant vendor documentation. Recheck package names, repository instructions, file paths, and configuration defaults for Ubuntu rather than assuming Debian-specific instructions still apply.
- Recreate automation. Set up service units, scheduled jobs, monitoring, and backup tasks. Confirm that each job points to the new data paths and runs under the intended account.
- Restore selectively. Import databases with the documented application procedure, copy application files with ownership and permissions preserved, and install certificates and secrets through your chosen secure process.
Use the old /etc tree to identify settings that need to be recreated, not as a replacement for Ubuntu’s new defaults. Compare each service’s old and new configuration and carry across only settings that are still needed and understood.
Best Value
Validate Ubuntu before changing DNS or traffic
Start services one at a time so problems are easier to isolate. Test from the Ubuntu host first, then from a separate network that resembles a player’s connection. A local process running successfully does not prove that the firewall, DNS, routing, or public address is correct.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →- Confirm each service starts and remains running; inspect its logs for errors.
- Check that expected ports are listening and reachable through the VPS firewall and any provider-level network controls.
- Verify local health checks or application endpoints, then connect to the game server externally as a player would.
- Confirm worlds, saves, plugins, mods, player data, and other persistent state are present and readable by the service account.
- Test database access, web panels, outbound mail if used, and any other dependent service.
- Check DNS resolution, IPv4 and IPv6 connectivity, and the actual addresses clients will use.
- Run a fresh backup from Ubuntu and verify that monitoring and scheduled maintenance work.
Fix errors on the replacement before cutover. Common migration failures include a missed data directory, an import performed in the wrong order, permissions that prevent the service account from reading files, an omitted port rule, a DNS record pointing at the old address, or a Debian-specific path carried over to Ubuntu. Use the service logs and the inventory to locate the mismatch rather than copying more of the old system indiscriminately.
Cut over with a defined rollback point
- Plan the final data handoff. If the game or application continues changing data, decide when to stop writes on Debian and how to copy the final changes to Ubuntu. Communicate any required maintenance window to players.
- Lower DNS TTL ahead of time when practical. This can reduce how long some clients continue using a cached record, but it does not make every resolver update instantly.
- Change the destination. Update DNS or the load-balancer target only after the Ubuntu server passes internal and external checks. If the provider preserves the same public IP, verify that the address now reaches the intended VPS and firewall.
- Monitor the new host. Watch service errors, resource use, connectivity, logs, and player reports. Confirm that backups and monitoring remain active.
- Retain the Debian rollback option. Keep the old VPS powered off or isolated, rather than deleting it, until the agreed rollback period ends and the Ubuntu copy has been checked.
If Ubuntu fails after cutover, revert traffic to Debian only if the Debian data is still suitable and you understand which copy has the latest writes. Two active servers accepting changes can create conflicting worlds or database state; avoid running both as authoritative servers unless the application is specifically designed for it.
Quick Recap
Migration mistakes that can turn into outages
- Replacing Debian repositories with Ubuntu repositories: this does not perform a supported distribution switch and can create an incompatible package mixture.
- Trusting a snapshot as the only copy: keep an independent off-host backup and test restoration before the destructive step.
- Rebooting or reinstalling over SSH alone: verify console, rescue, or serial recovery access first.
- Copying all of
/etconto Ubuntu: retain it for reference and restore service-specific settings selectively. - Forgetting state outside the main game folder: databases, attached volumes, proxy configuration, scheduled tasks, certificates, and secrets may be essential to the service.
- Switching DNS before external testing: verify connectivity from another network before sending players to the new host.
- Deleting Debian immediately after a successful boot: a booting server is not proof that the application, data, network, and backup process are all correct.
Practical migration checklist
- Choose a supported Ubuntu image available from the VPS provider and decide whether to replace or reinstall.
- Record the Debian release, services, package sources, users, network settings, storage, jobs, DNS, and required game data.
- Export databases and copy configuration, secrets, worlds, uploads, and persistent volumes to storage off the VPS.
- Test representative file and database restores.
- Verify provider console, rescue, or serial access before any reinstall or reboot.
- Install Ubuntu, rebuild services from Ubuntu-compatible instructions, and restore only reviewed data and settings.
- Validate services, files, ports, DNS, IPv4/IPv6, monitoring, and backups from local and external vantage points.
- Cut over traffic with a rollback plan, then retain Debian until the rollback window expires.
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.
