Disabling VMware High Availability for a single virtual machine allows administrators to exempt non-critical workloads from automatic cluster-level failover behaviors. You achieve this configuration through cluster-level virtual machine overrides in the vSphere management interface, which lets you customize restart priorities or completely turn off automated recovery features for specific guest systems without altering overall cluster availability protection.
Understanding Virtual Machine Overrides and Cluster Policies
Cluster Level Protection Mechanisms
VMware vSphere High Availability continuously monitors ESXi hosts within a designated cluster to detect hardware failures and guest operating system faults. When a physical server unexpectedly stops responding, the cluster orchestration service attempts to restart affected workloads on remaining operational hosts. Administrators use global cluster settings to define standard recovery actions, establishing a baseline level of operational continuity across the entire virtualized infrastructure pool.
Individual Workload Customization
Cluster-wide automation does not suit every hosted application or database service running inside your enterprise data center. Certain testing environments, staging servers, or legacy applications might corrupt data if restarted abruptly on alternative hardware nodes. Modifying individual behavior prevents unwanted automatic power-on sequences, giving IT teams granular control over specific virtual assets during unexpected hardware degradation events or rolling maintenance windows.
Configuring Overrides in vSphere
You implement single-machine exemptions by accessing the vSphere Client and navigating directly to your target cluster configuration panel. Selecting the virtual machine overrides option allows you to add a chosen guest and adjust its individual restart priority settings. Setting this parameter to disabled ensures that the cluster service ignores the selected virtual machine if its hosting server experiences a sudden power loss or network partition.
Impact on Monitoring and Isolation
Altering high availability rules for a single workload directly influences how the hypervisor treats guest operating system heartbeats and host isolation events. When you disable restart capabilities for that specific guest, built-in virtual machine monitoring features also cease taking automated corrective action upon application hangs. Understanding these dependencies helps technical staff prevent accidental service outages while maintaining strict compliance with internal recovery objectives.
Operational Procedures and System Comparison
Applying targeted configuration changes requires careful navigation through the vSphere web console to select appropriate cluster settings and modify individual restart parameters safely. Reviewing comparative operational impacts ensures your infrastructure team anticipates how customized virtual machines behave during unexpected hardware failures or scheduled data center maintenance events.
| Configuration Parameter | Default Cluster State | Custom Override State |
|---|---|---|
| VM Restart Priority | Use Cluster Settings | Disabled or Custom Level |
| Host Isolation Response | Power Off or Shut Down | Leave Powered On |
| VM Monitoring Status | Enabled via Global Policy | Disabled for Target Guest |
| DRS Migration Level | Automatic Balancing | Manual or Disabled |
Essential Verification Steps for Administrators
- Verify cluster permissions before editing virtual machine override tables in the management console interface.
- Open the cluster configuration view and locate the dedicated virtual machine overrides control panel.
- Select your target guest system and adjust the restart priority dropdown menu to disabled.
- Confirm your updated policy settings by reviewing the summary tab for that specific virtual machine.
Frequently Asked Questions
Why disable high availability for just one virtual machine?
Certain non-production or licensing-restricted applications suffer data corruption or license violations when restarted simultaneously on alternative physical hosts during a cluster failover event.
Does disabling high availability stop manual vMotion?
No, turning off high availability overrides only stops automated disaster recovery actions and does not restrict manual or automated DRS vMotion migrations.
Where can I find official configuration instructions?
Detailed technical documentation and step-by-step guidance are available through the Broadcom Support Knowledge Base portal.
Conclusion
Managing individual virtual machine high availability settings gives system engineers precise control over automated disaster recovery workflows. You can review your current cluster inventory and apply tailored virtual machine overrides directly through your vSphere administration dashboard today to secure vulnerable workloads.
