Administrator Guide

VASA Provider Restrictions
The following restrictions apply to the VASA provider:
The Storage Manager VASA provider can be registered to only one vCenter Server.
All ESXi and vCenter Server requests to the VASA provider are mapped to a single Storage Manager user.
The VASA provider does not support user-defined storage profiles. Only default system-defined storage profiles can be used in VM
Storage Policies.
Register the VASA Provider
You can register the VASA provider on a vCenter server, and manage it from the Servers view of Storage Center.
Register the VASA provider using one of the following methods:
When initially registering a vCenter Server in the Storage Manager client, select the Register VASA Provider check box.
For a vCenter Server that is already registered in the Storage Manager client, select Edit Settings and then select the Register
VASA Provider check box.
NOTE: After a software update, the follow error might occur:
Error registering VASA provider: Error running VMware method
[Method: RegisterVasaProvider] [Message: The VASA provider did not
respond]
Follow these steps to fix the error and register the VASA provider:
1. Open the file :msaservice\plugins\module_manager\product-metadata.json .
2. Change the VASA status to deploy.
3. Restart the Data Collector.
Related tasks
Register a VMware vCenter Server
Unregister a VASA Provider
Unregister a VASA provider to remove it from vCenter.
Prerequisites
CAUTION:
The VASA provider must be unregistered before you initiate any of these tasks:
Any action related to uninstallation, migration, upgrade, reinstalling of Storage Manager on same host with same IP
address
Uninstalling Storage Manager with the intention of reinstalling on another host
Changing the Storage Manager FQDN
Changing the Storage Manager IP address
Unregistering VASA will affects control plane operations on virtual volume VMs and datastores which are in use. It does
not affect data transfer between an ESXi host and the respective SAN storage.
Unregistering the VASA provider results in powered-off VVol VMs being shown as inaccessible and datastores as
inactive. To avoid prolonged control plane down time, minimize the period where the VASA provider remains
unregistered. After re-reregistration, there could be a delay for powered-off VMs and datastores to recover from being
inaccessible and inactive respectively.
Steps
1. Click the Servers view.
2. Select the Servers folder in the Servers pane.
172
Managing Virtual Volumes With Storage Manager