Browse this section

Allowing capacity for host maintenance and failures

Cluster capacity should include room for a host to be unavailable. If every host is fully allocated, a maintenance event or failure may leave too little capacity for the remaining workload. The required reserve depends on the availability design and application priorities.

Plan beyond the nominal total

  • Define how many host failures or maintenance events the design must tolerate and which workloads take priority.
  • Size remaining CPU and RAM for that scenario, including hypervisor overhead and peak demand.
  • Check storage, network and licence constraints as well as compute capacity.
  • Agree workload placement, maintenance sequencing and acceptance tests for the intended recovery behaviour.

Do not calculate usable production capacity by simply adding the labels on all hosts. Ask for both total resources and the capacity available under the agreed failure scenario. Review the reserve again when adding virtual machines or increasing allocations.

Was this guide helpful?

Related guides

When to choose a managed private cloud

A private cloud can help organise multiple virtual machines on a planned cluster, with shared operational controls and capacity management. It is most useful when the environment needs to b…

Understanding usable capacity in a vSAN cluster

Raw drive capacity is not the same as space available to virtual machines in a distributed storage cluster. Protection policies, layout, metadata, operational reserves and rebuild requireme…

Requesting virtual-machine changes safely

A request to change a virtual machine should identify both the new resource requirement and the effect on the application. Some changes can be made online in certain environments, while oth…

Need help applying this to your service?

Tell us your service reference and what you need to achieve. Never include passwords or private keys in a ticket.

Contact support →
← All knowledgebase topics