- vSphere API for Storage Awareness (VASA)
- NetApp HCI
- When attempting to migrate to a new vCenter, VASA may issues with the old vCenter keystore being persistent, leading to inaccessible VVol containers and a data unavailable situation.
- This article describes the procedure to clear the old keystore and generate a new one with the assistance of NetApp Technical Support.
- Configuring and working with VVols is explained in TR-4642: “VMware vSphere Virtual Volumes for SolidFire Storage Configuration Guide”.
- In TR-4642, here is an explicit warning about registering one VASA between two vCenters:
|Caution: Do not register a SolidFire VASA provider to more than one vCenter instance. The SolidFire VASA provider can only be registered to a single vCenter due to limitations with how vCenter handles SSL. A single vCenter can have multiple SolidFire clusters, but a SolidFire cluster cannot be shared between two instance of vCenter.|