+48 501 250 220

Consolidating old servers: moving to Proxmox with a way back

Several older Linux servers, the warranty has expired, and nobody knows exactly what runs where? We record your machines and set up a new host with Proxmox VE. Then we move the servers one at a time, with a tested backup and a way back for every step.

Request a server check What we do with Proxmox
  • Proxmox VE and KVM, single hosts and clusters
  • Full-stack and DevOps experience since 2012
  • Reply within one working day
Six small separate machines on the left, thin arrows run into a larger frame divided into compartments on the right, one compartment is filled orange

When consolidation is due

Typical signs:

  • Several physical servers each run one application or service.
  • The hardware warranty has expired, and spare parts are hard to get.
  • Nobody knows exactly what runs on which server and how it is backed up.
  • If a server fails, an application stops until the hardware is replaced.
  • Every machine needs its own updates, its own backups and its own power.

After consolidation, these servers run as virtual machines on a new host with Proxmox VE, or on several hosts if needed. What Proxmox is and what else we do with it is described under Proxmox.

Several separate servers of different heights on one base line, some drawn dashed as if ageing; an orange dot lights up on one server

How we move your servers

  1. Inventory

    We record every machine: services, data, dependencies, network, performance needs and existing backups.

  2. Plan

    We decide what moves as a virtual machine, what fits into a container and what can be switched off. The plan also sets the order, maintenance windows and the way back.

  3. New host

    We set up Proxmox VE with network, storage, access and backups. Before the first machine moves, we test the restore.

  4. Machine by machine

    Each machine moves on its own, in a maintenance window agreed with you. The old server stays unchanged until you have accepted the new machine.

  5. Handover

    You receive the documentation and a runbook for operation and recovery. If you wish, we take over ongoing support.

What you have after the move

  • less hardware that you have to maintain and replace
  • backups of all machines in one place, with a restore test
  • a snapshot before every change, which shortens the way back
  • documentation that shows what runs where

We calculate in the plan what you save on hardware, electricity and maintenance. We give a figure only once we know your servers.

One host holding four equal virtual machines in a two by two grid, one outlined in orange; on the right a backup box joined by a dashed line

Leave it, move it to Proxmox or put it in a container?

Criterion Leave the server as it is Virtual machine on Proxmox Container
Fits when the hardware is still under warranty, the system receives updates and the backup has been tested several servers with different services are to keep running a web application runs on Lucee, ColdFusion or PHP and can be described in files
Effort low: test the backup, apply updates inventory, new host, move of every machine describe the environment, test on staging, switch over
Way back not needed the old server stays unchanged until acceptance the existing environment remains until acceptance

When the move is not worth it

With a single small server, a Proxmox host of its own is often not worth it. A virtual machine at a provider or a container is then usually simpler. A server with a valid warranty and a supported system can also stay where it is, as long as updates and backups are in order.

If a server runs a system that no longer receives updates, virtualisation does not solve that. It only moves the problem onto new hardware. In that case, a server upgrade belongs in the plan.

A system keeps running along a straight line; the branch to a new, dashed platform is blocked by an orange bar

The first step: a server check before the plan

Server check

For companies with Linux servers that nobody knows well any more: before an upgrade, after the administrator has left or when a client asks about backups.

  • Version and support status of the operating system and services
  • Hardening: SSH access, firewall, open services and TLS certificates
  • Updates: what is missing and how they have been applied so far
  • Backups: what is backed up and whether a restore test is documented
  • Monitoring and logs: what is monitored and what is missing
  • List of findings in order of priority

At this stage we change nothing on the server. The check does not cover the application or its code. That is what the legacy review is for. We agree the scope and price in the intro call and confirm them in writing before we start. If you wish, you then receive a quote for ongoing support.

What the result contains

A written list of findings in order of priority, with recommendations on hardening, updates, backups and monitoring, plus an upgrade plan with maintenance windows. Both are yours.

Request a server check

Questions about consolidating on Proxmox

Is Proxmox worth it for one or two servers?

Often not. With a single small server, a virtual machine at a provider or a container is usually easier to run. A Proxmox host of your own pays off when several servers are brought together or the old hardware has to be replaced anyway.

We work out in the plan what pays off for you: hardware, electricity and maintenance effort. If the answer is that your server can stay as it is, we tell you that too.

Do we need new hardware for Proxmox?

Usually a new host makes sense, since the old servers are exactly what is being replaced. An existing server can be the host if it is still under warranty and has enough power, memory and disk space for all machines.

The host can stand on your premises or be rented hardware at a provider. What you need is set out in the plan, before you buy anything.

How long is the server unavailable during the changeover?

That can only be said after we have looked at your system. We do not promise a changeover without any interruption. We rehearse the procedure beforehand on a copy, carry out the changeover in a maintenance window agreed with you and keep a rollback ready.

With a rebuild, the new server is set up alongside the old one, and the interruption is usually limited to the switch itself. With an upgrade of the existing system, services and the server restart, so an interruption is to be expected.

What happens if something does not work after the move?

Then we switch back to the old server. It stays unchanged until you have accepted the migrated machine. For each maintenance window we define in advance how we measure success and at what point we switch back.

We rehearse the move on a copy first. The old server is switched off only after acceptance.

Do we need a Proxmox cluster?

Not necessarily. For many companies, one host is enough, with backups whose restore has been tested. A cluster of several hosts pays off if your machines should keep running on another host during maintenance or when a host fails. That takes more hardware and a suitable network.

A cluster does not replace a backup. Anything that was deleted or altered by malware is deleted or altered in the cluster too.

Do you cover weekend duty from time to time?

Yes. Support and emergencies are covered around the clock (24/7), weekends included. For other enquiries we are available Monday to Friday, 9:00 to 17:00 Central European Time, and we reply within one working day.

In 20 minutes we work out which first step fits your system

You tell us the goal and the current state, and we say openly whether and how we can help. Reply within one working day, no obligation.

Book an intro call How we work
Phone (German, Polish, English) +48 501 250 220
Email Email

Reachable: Monday to Friday, 9:00 to 17:00 Central European Time; support and emergencies around the clock (24/7)