Servers, Storage and Virtualization · #49

Online Hyper-V Cluster N+1 Capacity Planner

Tests for each host failure whether the VMs can be placed on the remaining hosts by RAM.

  • Data is processed in your browser and not sent to a server
  • Export: CSV

Tool

Per line: name;RAM GiB

Per line: name;RAM GiB;current host (assigned/startup RAM).

For parent partition and hypervisor.

What does this tool do?

A cluster may show 'enough free RAM in total', yet if one large VM fits on no single host it cannot start during failover. The tool runs a failure scenario per host, places moving VMs largest first on the host with the most free space and separates definite failures from placement-order (heuristic) failures.

How to use it

  1. Enter hosts as name;RAM GiB and VMs as name;RAM GiB;host, one per line.
  2. Enter the hypervisor reserve per host and press Calculate.

Fields

Host list
Per line: name;RAM GiB
VM list
Per line: name;RAM GiB;current host (assigned/startup RAM).
Reserve per host
For parent partition and hypervisor.

Worked example

InputValue
Host list
HV01;384
HV02;384
HV03;384
VM list
SQL01;160;HV01
APP01;48;HV01
DC01;8;HV01
EXCH01;96;HV02
RDS01;48;HV02
RDS02;48;HV02
ERP01;128;HV03
WEB01;32;HV03
FS01;48;HV03
Reserve per host16

Expected result: When any one of the three hosts fails, its VMs fit on the remaining two: the cluster is N+1 compliant.

If HV01 fails, SQL01 (160 GiB) lands on HV02, APP01 and DC01 on HV03. Adding a new 128 GiB VM can change this; run the tool again before adding.

Second scenario

InputValue
Host list
A;128
B;128
C;128
VM list
BIG;80;A
V1;64;B
V2;64;C
Reserve per host0

Expected result: If A fails, total free RAM is 128 GiB, but the 80 GiB BIG VM fits on no host (64 GiB free each): definite failure.

Method and assumptions

Host capacity = RAM − reserve. In a failure scenario the moving VMs are sorted largest first and placed on the host with the most free RAM (worst-fit).

If a VM is larger than the largest free space on any host, or the total exceeds total free space, the result is 'definite failure'; otherwise a failed placement is marked 'heuristic' — a different placement might fit.

Using the result and troubleshooting

For failing scenarios rebalance VMs, review dynamic memory minimums or add host RAM. Set Hyper-V start priorities for important VMs.

Limits and common mistakes

  • Only RAM is checked; CPU, storage, network capacity and anti-affinity rules are not considered.

Frequently asked questions

Which value should I enter for VMs with dynamic memory?

Failover needs at least startup RAM; for a safe estimate enter the currently assigned RAM.

Related tools and service

Related service: Virtualization and Data Management

Systems online tools · See all online tools