Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Behavior of vSphere HA VM Component Protection APD policies (78278)

Last Updated: 4/2/2020Categories: InformationalTotal Views: 5760Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Details

This article clarifies the behavior of vSphere HA's response to All Paths Down (APD) events. The behavior itself has not changed in 7.0 when compared to previous releases like 6.5 or 6.7.

To view the APD Failure Response section events from vCenter UI, go to Hosts and Cluster > <click on a cluster of choice> > Configure tab > vSphere Availability >  click Edit > Expand Datastore with APD item.

Currently, you have four options to choose:

Disabled

Issue Events

The Disabled and Issue Events do not alter anything for the VM itself. The former does nothing while the latter issues some events that are visible on the vCenter GUI.

Power off and restart VMs - Conservative restart policy

Power off and restart VMs - Aggressive restart policy

When an APD occurs for a datastore on a host, if either "Conservative" OR "Aggressive" options are selected, vSphere HA will first try to find a host where it can be powered on. If it can find one, the VM is terminated and attempted to power on at the selected host.

If a suitable host cannot be found is when there is a difference of behavior between "Conservative" and "Aggressive".
If the "Aggressive" behavior is chosen at the point where no suitable host was found to power on the VM, a further check is made to see if there is a network partition on the cluster. If partition exists, the VM is terminated (even when there was no suitable host). This is the key difference in behavior between "Conservative" and "Aggressive". "Conservative" will not try to terminate a VM even if there is a network partition.
For more information on these options and other reasons why a VM could not be failed over, see Datastore Inaccessibility is not resolved for a VM.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere

Related Versions:

VMware vSphere 7.0.x

VMware vSphere 6.7.x

VMware vSphere 6.5.x

Take Our Survey

Support Assistant