Virtualization and Servers for Business
A virtual environment brings the business’s servers together on one or more hosts, and lets you back them up, move them and restore them without depending on a specific physical machine. We plan, build, migrate and maintain Hyper-V, VMware and Proxmox environments.
All your servers
in one place
An organized virtual environment lets you see all the servers, back them up and move them between machines, without buying hardware for every new need.
- Hosts and virtual machines in one view
- Image-level backup and restore of an entire server
- Planned migration between platforms and from physical to virtual (P2V)
Who it’s for
Businesses with several old physical servers
A separate server for each system, some of them already out of warranty. Consolidating into a virtual environment (server consolidation) reduces hardware and makes backup and maintenance easier.
VMware environments weighing what’s next
Organizations running VMware that are considering a move to another platform following the licensing changes, or want to review their options before renewal.
Businesses that need high availability
Systems that must not stop because of a fault in one server, and that justify a cluster with two or more hosts and shared storage.
Sound familiar?
These are the situations in which the server environment turns from an asset into a risk.
- One physical server runs the whole business, and there’s no replacement if it fails (single point of failure)
- A virtualization host that hasn’t been updated since it was installed
- A VMware or Windows Server version that is out of support (end of support)
- Virtual machines that exist for reasons nobody knows (VM sprawl)
- The host’s storage is filling up with forgotten snapshots
- The backup saves files, but there’s no quick way to bring back an entire server
What the virtualization service includes
From planning and setup to ongoing maintenance of the hosts.
Microsoft Hyper-V
Setting up and managing Hyper-V hosts and clusters, including integration with Active Directory and image-level backup.
VMware vSphere and ESXi
Managing existing vSphere environments, vCenter and version upgrades, and planning ahead in light of the licensing changes.
Proxmox VE
Setting up Proxmox environments, clusters, storage and Proxmox Backup Server, as an alternative to VMware or as a new environment.
Migration and P2V
Moving servers from physical to virtual and between platforms, with a plan, testing and a coordinated downtime window (maintenance window).
Clusters and high availability
Two or more hosts with shared storage, so that a fault in one host moves the machines to another host (failover).
Storage
NAS, iSCSI and NFS, capacity and performance planning, RAID and disk health monitoring.
Host maintenance
Host and firmware updates, snapshot cleanup, resource monitoring and remote management through iDRAC or iLO.
Securing the virtualization environment
Management interfaces on a separate network, least privilege, MFA for management, and a backup the host itself can’t delete (immutable backup).
What we take care of, in detail
Platforms and setup
- Planning and setting up on-prem virtualization environments in the customer’s data center
- Microsoft Hyper-V: standalone hosts and Failover clusters, managed through Windows Admin Center or SCVMM
- VMware vSphere / ESXi and vCenter: managing existing environments, upgrades and planning in light of the licensing changes
- Proxmox VE: hosts and clusters, Ceph or ZFS storage, and Proxmox Backup Server
- Physical servers: installation, warranty, remote management (iDRAC/iLO)
- Capacity planning: CPU, memory and storage based on the actual workloads, with room to grow
Migration and availability
- Migration between platforms (VMware → Hyper-V / Proxmox) and from physical to virtual
- P2V: moving old physical servers to virtual machines, with testing before and after the move
- Clusters and high availability
- Moving machines between hosts (Live Migration / vMotion) for maintenance without downtime
- Replicating machines to a secondary site (replication) as part of a DRP plan
Storage, maintenance and security
- Storage: NAS, iSCSI, NFS
- Version upgrades and host maintenance
- Firmware and driver updates for servers and disk controllers
- Managing and cleaning up snapshots, monitoring capacity and resources
- A separate management network for the hosts, least privilege and MFA for the management interfaces
- Image-level backup (Veeam, Proxmox Backup Server) with a copy that can’t be changed (immutable)
From the first conversation to an organized routine
- 1
Mapping the environment
A list of the servers, systems, dependencies, licensing and the state of the hardware.
- 2
Planning
Choosing a platform, calculating resources and storage, and a migration plan with time windows.
- 3
Setup and migration
Setting up the hosts, moving the servers in phases and checking each system after the move.
- 4
Ongoing maintenance
Updates, monitoring, snapshot management, backup and documentation of the environment.
What to know before building or migrating a virtualization environment
The virtualization environment brings all of the business’s servers together in one place. That saves hardware and makes management easier, and it also means that a fault or a breach in the host affects all the servers at once.
A snapshot is not a backup
A snapshot saves the state of the machine on the same storage, and is meant for a quick rollback before a change. Snapshots left in place for days and weeks slow the machine down and bloat the storage, and they won’t help if the host or the storage itself fails. A real backup is kept somewhere else, and is tested with a restore.
The host’s management interface is a critical asset
Ransomware groups attack ESXi and Hyper-V hosts directly, because encrypting the host takes down all the servers in one move. The management interfaces should sit on a separate network (management network) that isn’t reachable from employee workstations, with MFA, least privilege and regular updates.
Migration starts with mapping
Before moving a server, you check what it depends on (dependencies): licenses tied to hardware, static addresses, services that talk to each other and old drivers. Moving from VMware to Hyper-V or Proxmox is possible with well-known tools, but it requires checking every machine and a rollback plan in case something doesn’t come up.
High availability is capacity planning
A cluster works only if the remaining hosts can carry all the machines when one of them fails (N+1). So memory and CPU are planned with headroom, along with storage that all the hosts can see and a separate network for cluster and storage traffic.
A version out of support is a growing risk
A host that doesn’t receive security updates keeps working, but every vulnerability published for it stays open. Tracking the end-of-life dates of the platform, the operating systems and the hardware makes it possible to plan the upgrade and the budget in advance, rather than under pressure after a failure.
Guide: Virtualization for business: Hyper-V, VMware or Proxmox
It depends on the existing environment, the licensing and your needs. Hyper-V is convenient for businesses that already work with Windows Server and Microsoft licensing. Proxmox VE is open source with an optional support subscription, and suits both small and large environments. VMware is common in organizations, and its licensing changes are leading many to look at alternatives. The recommendation comes after mapping.
The move itself requires a short downtime window for each server, so it is planned in phases and during quiet hours. Before the move each machine is checked, and afterwards we make sure the systems come up and work. The old environment stays available until it’s clear everything is fine.
A small business is usually well served by one host with a good backup and a recovery plan (DRP). A cluster pays for itself when hours of downtime because of a hardware failure hurt the business more than the cost of an additional host and shared storage. The decision is made based on the RTO the business needs.
Usually it can be moved to a virtual machine (P2V), so it no longer depends on aging hardware. Before the move we check licenses tied to the hardware and software that requires a physical device.
Both options exist. The environment can be set up in the business’s server room, or run on servers in the data center we manage and in the cloud. The decision depends on the software, the internet connection, regulatory requirements and cost.
Separate the management interfaces onto their own network, restrict permissions, enable MFA and keep the hosts updated. The most important part is a backup kept outside the environment, with a copy that can’t be deleted or encrypted from within the host (immutable backup), and periodic restore tests.
More you can centralize with us
System Administration
Ongoing administration of Windows and Linux servers, Active Directory and Entra ID, permissions, security updates and monitoring, with documentation and change management.
Backup, recovery and continuity
Cloud and off-site backup for servers, workstations, websites and M365, with restore tests and DRP planning.
Virtual servers and cloud
Managed VPS and dedicated servers on infrastructure we manage, terminal servers (RDS), and public, private and hybrid cloud, with backup, hardening and cost control.
Planning a new server environment or a move off VMware?
Tell us briefly about your business and what concerns you about your IT. We’ll get back to you to understand what you need and suggest a way of working that fits.
Business hours: Sunday to Thursday, 09:00 to 17:00
Existing client? Open a support ticket