Support for Debian 11 ended on 31 August 2026, and for CentOS 7 on 30 June 2024 (As of 2026-10). We will upgrade your server, or plan and carry out the move to Debian. We also work with Proxmox VE 8 and with physical servers that we move to Proxmox.
Proxmox VE: setting up, backing up and upgrading virtualisation
We set up Proxmox VE on your hardware and back up the virtual machines with tested restores. Updates up to the next major version follow a plan. We move old physical servers to Proxmox one machine at a time, with a way back.
- Proxmox VE and KVM, single hosts and clusters
- Full-stack and DevOps experience since 2012
- Reply within one working day
Where we use Proxmox
Proxmox VE is a virtualisation platform based on Debian. One host runs several virtual machines, each with its own system, its own services and its own backup. We use Proxmox where several servers are to be brought together, on your premises or on rented hardware at a provider.
Our engineers run KVM and Proxmox, as well as Debian and the Linux servers inside the virtual machines. For a single web application, a container is often the better choice; see Docker.
Typical tasks with Proxmox
- Setting up new hosts: network, storage, access, firewall and administration access through a VPN.
- Backups of the virtual machines, also outside the host, with a regular restore test.
- Updates of the hosts in a maintenance window, and upgrades to a new major version following the vendor's instructions.
- Clusters of several hosts, so that virtual machines can be moved to another host for maintenance.
- Moving old physical Linux servers to Proxmox, described under Server consolidation on Proxmox.
- Monitoring of hosts, storage space and backups, with an alert when something fails.
- Documentation and a runbook for your team.
Upgrading to a new major version
Proxmox VE can be upgraded to the next major version without reinstalling the host. Before the upgrade, the vendor requires a valid and tested backup and provides a checker that reports obstacles in advance.
We back up all machines, test the restore, resolve what the checker reports and carry out the upgrade in an agreed maintenance window. In a cluster we go host by host and first move the machines to another host. With a single host, we plan for an interruption.
A cluster does not replace a backup
A cluster of several hosts helps when a host fails or is under maintenance. It does not help against deleted files, an error in the application or malware, because the change affects the machine on every host. For that you need backups outside the cluster, with a tested restore.
For many companies, a single host with good backups is enough. Whether a cluster pays off for you is something we work out in the plan.
Technologies and scope
| Area | Scope |
|---|---|
| Virtualisation | Proxmox VE and KVM, single hosts and clusters |
| System | Debian and Ubuntu in the virtual machines, Debian as the basis of Proxmox VE |
| Containers | Docker for Lucee, Adobe ColdFusion and PHP |
| Databases | MySQL and MariaDB, also with Galera |
| Network and security | Firewall, segmentation and administration access through a VPN |
| Logs and visibility | Loki for central logs, Grafana for dashboards |
Typical starting points with servers and virtualisation
-
-
We move your Lucee, ColdFusion or PHP application from classic hosting into containers without rewriting it. That lets you rebuild, update and relocate the environment. Security updates for PHP 8.2 end on 31 December 2026 (As of 2026-10).
The first step: a server check with written results
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.
Questions about Proxmox and virtualisation
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.
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 do we gain by moving to a container?
An environment that can be rebuilt. The same version and configuration apply on the developer's machine, on staging and in production, recorded in the repository instead of in one person's head. We test new versions of PHP, Lucee or ColdFusion alongside production and can roll them back. Moving to another server or another provider also becomes easier.
A container fixes no bug in the code and does not bring an unsupported version up to date. It only makes those changes easier.
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.
Not sure which service fits your system?
Describe your system in two sentences. We will tell you which service fits and whether an entry product at a fixed price is the right first step.