VVOL datastore inaccessible after moving hosts to a different vCenter server

Products

• VMware vSphere ESXi

Issue/Introduction

Symptoms

• The VVOL datastore appears in an inaccessible state in the vSphere Client.
• Any attempt to power on a powered-off VM residing on the VVOL datastore results in the VM transitioning to an invalid state.
• VMs that are already powered on remain functional and unaffected.
• This issue may occur if the vCenter Server has been rebuilt from scratch, leading to a loss of vVOL management metadata.

Issue Validation

• Verify Protocol Endpoints Configuration & Accessibility:
  
  Navigate to Host > Configure > Protocol Endpoints in the vSphere Client to check if protocol endpoints are properly configured and accessible.

• Alternatively, use the following ESXi command:
  
  esxcli storage vvol protocolendpoint list

Sample output:

esxcli storage vvol protocolendpoint list
naa.xxxxxxxxxxxx
Host Id: naa.xxxxxxxxxxxx
Array Id: com.purestorage:9
Type: SCSI
Accessible: true
Configured: true
Lun Id: naa.xxxxxxxxxxxx
Remote Host:
Remote Share:
NFS4x Transport IPs:
Server Scope:
Server Major:
Auth:
User:
Storage Containers:

Environment

VMware vCenter Server 7.x
VMware vCenter Server 8.x

Cause

The VASA provider is not registered with the vCenter Server that the hosts are connected to, leading to the VVOL datastore being marked as inaccessible in the vSphere Client. The VASA provider facilitates communication between vCenter Server, ESXi hosts, and the storage system, enabling the creation and management of Virtual Volumes (vVols). Without the VASA provider, vSphere cannot properly manage VMs residing on the VVOL datastore. 

Cause Validation:

• Check the VVOL VASA Provider Status:
  
  Run the following command on the ESXi host: esxcli storage vvol vasaprovider list
  
  Sample output:
  
  esxcli storage vvol vasaprovider list
<VASA Provider name>
VP Name: <VASA Provider name>
URL: https://<VASA Provider IP>:<Port>/vasa/version.xml
Status: syncError
Arrays:
Array Id: Storage:0068c7e1d64238ff
Is Active: true
Priority: 0
  
  If the syncError state is displayed, it indicates that the VASA provider is not functioning correctly. A properly functioning VASA provider should have a status of online

• Validate VASA Provider Registration in vCenter:
  
  Navigate to vCenter > Configure > Storage Providers and check if the VASA provider is registered.

  
  
  The VASA provider is missing, it is not registered on the new vCenter Server, which contributed to the issue.

Resolution

To enable the use of  VVOL storage, register the VASA provider on the vCenter Server.

1. Navigate to Global Inventory Lists > vCenter Servers Instance > Configure > Storage Providers.

2. Click on Add

   

3. The New Storage Provider screen opens. Enter the VASA provider registration information and click OK. The name, url, username and password will be shared by your storage provider.

   

4. When registration is complete, the provider displays as Online.

   

   The vvol datastore will automatically restore accessibility once the vasa provider is registered and is online