Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

About the *(Any) Storage Profile (2045534)

Symptoms

  • In the list of Storage Profiles, you see a profile named *(Any).
  • When you try to delete the *(Any) Storage Profile, you see the error:

    Storage Profile *(Any) cannot be deleted since it is currently in use.

Purpose

This article provides information on the *(Any) Storage Profile and the caveats associated with it.

Resolution

The Storage Profiles feature was first introduced in vSphere 5.0. It enables users to map the capabilities of a storage system to a profile. You can create a user defined storage capability, assign a storage capability, create a virtual machine storage profile, and enable the storage profile on the host/cluster at the vSphere layer only.

Storage Profiles are added to the provider virtual datacenter (vDC). You can add a subset of Storage Profiles to an organization vDC. By selecting the Storage profile matching their requirements, users can ensure the virtual machines they created utilize the appropriate datastore. Enabling Storage Profiles allows multiple tiers of storage within a single virtual datacenter.

To view the Storage Profiles available in vCloud Director 5.1, click Storage Profiles under vSphere Resources. If you cannot view the Storage Profile you wish to see, right-click the vCenter Server and click Refresh Storage Profiles. This does a force pull of the Storage Profile inventory immediately for that particular vCenter Server, which by default is done every five minutes.

Unlike vCloud Director 1.5, which did not have the concept of Storage Profiles, individual datastores cannot be added to a provider vDC, instead the datastores associated with Storage Profiles are added to the provider vDC in vCloud Director 5.1.

By default, a *(Any) Storage Profile is created. This denotes all the datastores presented and available to the hosts used in the vCloud Director, irrespective of whether the datastore provides any storage capabilities. (This normally includes local datastores.) The *(Any) Storage Profile is propagated to all the provider vDCs, organization vDCs, vApps, virtual machines, etc when vCloud Director 1.5 is upgraded to version 5.1.

Since this pseudo *(Any) Storage Profile is automatically inherited and vCloud Director does not provide the ability to choose the vApp or virtual machine placement during deployments, the use of local storage can present problems with application performance, availability, SLAs, etc as there will be no use of HA or DRS. Therefore VMware suggests that you disable the local datastores immediately after upgrading to vCloud Director 5.1.

To disable local datastores:
  1. Click the Manage & Monitor tab, then click Datastores in the left pane.
  2. Right-click the local datastore name and click Disable.
Once this is done, the *(Any) Storage Profile is not used and can be disabled and then removed.

Note: Only unused and disabled Storage Profiles can be removed.


To disable the *(Any) Storage Profile from the organization vDCs:
  1. Click the Manage & Monitor tab, then click Organization vDCs to list the organization virtual datacenters.
  2. Double-click the organization vDC where you want to disable the *(Any) Storage Profile.
  3. Click the Storage Profiles tab which lists the *(Any) Storage Profile.
  4. Right-click the *(Any) Storage Profile and click Disable.

To disable the *(Any) Storage Profile from the provider vDCs:
  1. Click the Manage & Monitor tab, then click Provider vDCs to list the provider virtual datacenters.
  2. Double-click the provider vDC where you want to disable the *(Any) Storage Profile.
  3. Click the Storage Profiles tab which lists the *(Any) Storage Profile.
  4. Right-click the *(Any) Storage Profile and click Disable.

Note: If you do not disable and remove the *(Any) Storage Profile from the organization vDC, you will not be able to remove it from the provider vDC.

Additional Information

For related information, see:

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 4 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 4 Ratings
Actions
KB: