Virtualisation runs several separate systems on shared physical hardware. Each virtual machine has its own environment while the hypervisor manages resources. This simplifies some operations without removing capacity planning, licensing, redundancy or service dependencies.
What changes for the service
Instead of tying an application to a separate physical machine, you get a managed virtual machine. It can be moved or restored within the chosen platform’s capabilities. Operation still depends on supported operating systems, drivers, networking and licensing.
Collect actual workload measurements before consolidation. The number of old servers does not determine the new host’s capacity. Account for peaks, disk activity, background backups and concurrent jobs rather than average CPU load alone.
Shared hardware creates shared dependencies
Several virtual machines on one host depend on its power, storage and network. For example, consolidating email, files and accounting reduces physical machines, but a host failure affects all those services. Account for this before purchasing.
High availability requires deliberately designed components and failover testing. A second host alone does not prove storage independence or sufficient remaining capacity. Agree which services must continue after a specific failure.
Snapshots and backups serve different purposes
A snapshot can help return to a pre-change state but often depends on the same storage and disk chain. It is not an independent full backup. Check snapshot type and data consistency against hypervisor and application documentation.
Long-lived snapshots can complicate storage management. Define supported creation, space monitoring and cleanup procedures. Separately test independent backup restoration, including required keys and configuration.
| Mechanism |
What to check |
|
Virtual machine |
Resources, application and dependencies |
|
Snapshot |
Type, consistency and storage dependency |
|
Independent backup |
Availability and actual restoration |
Acceptance includes management and recovery
After migration, test user operations, performance, network rules and monitoring. Test host reboot and individual machine restoration under an agreed scenario. Criteria should reflect the service rather than only the hypervisor dashboard.
Hand over the machine and dependency map, access, backup procedures and update rules. Reassess capacity and licences as workload changes. Virtualisation provides flexibility when the environment remains manageable and understood by support staff.
Sources and further reading
