What is included

We both implement from scratch and maintain an existing environment, including migrating physical servers.

Discuss the scope

Design

Sizing the resources for the planned machines with headroom for peak load.

Deployment

Installing and configuring the hypervisor, the networking and the storage.

Server migration

Moving physical machines into virtual ones with minimal downtime.

Resource allocation

Limits and priorities so one machine cannot take everything from the others.

Snapshots and backups

A routine for snapshots before changes plus proper backups of the machines.

Redundancy

A second node that restarts the machines automatically if the first fails.

How the work runs

Implementation for a small infrastructure takes one to two weeks. Servers are migrated one at a time in agreed windows.

01

Audit

What the servers are, what load they carry, what can be virtualised and what cannot.

02

Design

The node configuration, the network and storage design and the migration plan.

03

Deployment and migration

The hypervisor, then the machines migrated one by one with each verified.

04

Routine

Snapshots, backups, resource monitoring and an action plan if a node fails.

A snapshot is not a substitute for a backup. It lives on the same storage and disappears with it, and it slows the machine down if it is left for weeks. A snapshot is taken before a change and deleted once verified, while the data is protected by proper backups.

Frequently asked questions

The overhead of modern hypervisors is small and usually unnoticeable. Slowdowns come from oversubscription, when more machines are packed onto a node than it can carry. That is a question of sizing rather than of the technology.

Yes, and it is common practice. It is important to allocate enough resources and not to place it on the same node as machines generating heavy disk load. The disk requirements stay the same: solid state drives only.

Without redundancy, every machine on it stops, and that is the main risk of virtualisation: all the eggs in one basket. So critical infrastructure needs a second node, and everything else needs reliable backups and a clear recovery plan.

We will implement virtualisation

Tell us how many servers you have and what runs on them. We will size the node and propose a migration plan with no downtime.