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

vSAN host fails to enter Maintenance Mode with 'Full data migration' option selected (78149)

Last Updated: 9/10/2023Categories: TroubleshootingTotal Views: 13309Language:
Chinese (Simplified)JapaneseEnglish

3 like this article

Subscribe to get an email
newsletter with new updates

3 people found this helpful Please provide article feedback:

Symptoms

A host will fail to enter maintenance mode using Full Data Evacuation if the cluster is not able to meet the minimum number of fault domains that the storage policy requires which is N+1.

Purpose

Awareness of vSAN cluster requirements.

Cause

vSAN requires a certain number of hosts to be active with disk groups contributing capacity and resources in vSAN in order to provide fault tolerance. If the requirements cannot be met, vSAN will fail the pre-check it performs when placing a host into maintenance mode.

See the below documentation for further information:
Managing Fault Domains in Virtual SAN Clusters
Design and Operation Considerations When Using vSAN Fault Domains
Fault Domains

When entering Maintenance Mode a "What-if" scenario will be run. If the result is, that after entering Maintenance Mode only not enough Fault Domains will be available the Full Data migration will fail.

The clomd.log will provide the related error message:
LOM_CheckClusterResourcesForPolicy: Not enough Upper FD's available. Available: 3, needed: 4
LOM_CheckClusterResourcesForPolicy: Not enough Upper FD's available. Available: 4, needed: 5

Resolution

If full data migration is needed, then a 5th host for RAID5 or 7th host for RAID6 is required to be added to the vSAN cluster first.
* Otherwise the Storage Policy can be changed to FTT=1,FTM=RAID1

Please be aware that during the change from RAID5 or RAID6 to RAID1, new components will be created first and the old ones deleted once the rebuild has completed. Make sure that there is sufficient space in the cluster before proceeding.

Workaround

Select Maintenance Mode 'Ensure Accessibility' option - note that all data using RAID5/6 Storage Policies will be in a reduced redundancy state until the host has exited Maintenance Mode and the data resynced back to compliance.

Related Information

A Closer Look at vSAN Maintenance Mode
Place a Member of vSAN Cluster in Maintenance Mode

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
在 SR-IOV 情况下使用 Intel 网卡 82599/X520 时，处于 VLAN 中继模式的 VLAN 接口之间出现问题 (78245)

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSAN

Related Versions:

VMware vSAN 8.0.x

VMware vSAN 7.0.x

VMware vSAN 6.x

Take Our Survey

Support Assistant