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

Unable to delete a vSAN Storage Policy that shows no VMs associated with it. (76844)

Last Updated: 8/6/2023Categories: TroubleshootingTotal Views: 4000Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

When attempting to delete a Storage Policy via the vSphere Web Client the task fails stating that the policy is in use:
The selected VM storage policy is in use and cannot be deleted

Purpose

This article outlines potential causes of being unable to delete a vSAN Storage Policy.

Cause

There are a number of ways a vSAN Storage Policy can be in use other than being applied to registered VMs in vCenter:

There are VMs residing on vsanDatastore with the applied Storage Policy in use that are no longer registered in inventory - these will not show in the 'VMs' tab of the Storage Policy.

There are healthy/unhealthy Unassociated Objects with the Storage Policy applied. Procedures for identifying Unassociated vSAN objects. (70726)

The vSAN Performance stats Object has this Storage Policy applied:

Cluster > Configure > vSAN > Services > Performance Service > Stats object storage policy

A vSAN namespace is being used for host logging (unsupported) and has this policy applied.

Other non-VM Objects are using the Storage Policy including but not limited to:

ISOs or other miscellaneous use namespace directories

Content Libraries

The Storage Policy in question is set as the vsanDatastore default policy:

Datastores > vsanDatastore > Configure > Default Storage Policy

The policy is the 'vSAN Default Storage Policy' that is automatically generated on cluster creation - this cannot be renamed or deleted, only changes to the rules of this policy can be changed.

Resolution

Check to see if any of the examples listed in the "Cause" section above are using the vSAN Storage Policy to be deleted. If so then either delete the unassociated objects if no longer in use, otherwise change the Storage Policy to a different policy other than the one to be deleted.

Note: Open a case with vSAN Support for assistance with deleting unassociated objects

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
vSphere 6.5 およびその互換性のある VMware 製品の更新手順 (2147289)

Result 1 of 1

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