Virtualization lets one physical server run many workloads. Sizing it correctly is the key to performance.

Start with the workloads

List the virtual machines you’ll run and their CPU, RAM, storage, and growth needs, plus peak usage.

CPU

Fast cores matter for databases and line-of-business apps. For general workloads, a vCPU-to-physical-core ratio of roughly 2:1 to 4:1 is common. Critical systems should be closer to 1:1.

Memory

RAM is usually the first limit. Avoid heavy overcommitment on production hosts, and leave headroom for the host itself and for failover.

Storage

Match the storage to the workload.

– SSD/NVMe for databases and busy VMs

– RAID 10 or similar for a balance of speed and resilience

– Plan for capacity growth and IOPS, not only terabytes

Networking

Use separate networks or VLANs for management, VM traffic, and storage or migration. 10 GbE is increasingly the practical standard for storage and live migration traffic.

Redundancy

– Two hosts allow failover clustering or replication

– Plan “N+1” capacity so one host can carry the load if another fails

– Redundant power supplies and network connections

Licensing

Windows Server Standard licenses cover two virtual machines per fully licensed host. Datacenter covers unlimited VMs. Run the numbers, since the right choice depends on VM count.

Backup and monitoring

Choose backup software that understands Hyper-V and monitor host and VM performance.

DBR Soft designs, builds, and supports virtualization environments. Contact us for a sizing review. Contact us for more details.