While it is highly unlikely that the VASA Provider database will become corrupted, it is possible to recreate the VP database from metadata stored in ONTAP If the above scenario is not applicable to y...While it is highly unlikely that the VASA Provider database will become corrupted, it is possible to recreate the VP database from metadata stored in ONTAP If the above scenario is not applicable to your own, please see the VASA Provider Disaster Recovery Resolution Guide If you have provisioned a new, replacement OTV appliance, please use How to recover when VASA Provider has been lost or is inaccessible
Applies to NetApp ONTAP Tools for VMware vSphere (OTV) 9.6 and later NetApp VASA Provider Description If the VASA Provider (VP) virtual appliance has been lost, rendered inaccessible, or otherwise non...Applies to NetApp ONTAP Tools for VMware vSphere (OTV) 9.6 and later NetApp VASA Provider Description If the VASA Provider (VP) virtual appliance has been lost, rendered inaccessible, or otherwise non-functional, it might be necessary to perform a VP Disaster Recovery vVol metadata is stored in Data ONTAP (in a .vp_metadata file present on the backing flexvols associated with vVol datastores) The recovery commands allow the VASA Provider to reload this metadata into its database
Applies to ONTAP Tools for VMware vSphere (OTV) 9.6 and later ONTAP VASA Provider Description If the VASA Provider (VP) virtual appliance has been lost, rendered inaccessible, or otherwise non-functio...Applies to ONTAP Tools for VMware vSphere (OTV) 9.6 and later ONTAP VASA Provider Description If the VASA Provider (VP) virtual appliance has been lost, rendered inaccessible, or otherwise non-functional, it might be necessary to perform a VP Disaster Recovery. VVOL metadata is stored with the VVOL objects resident in Data ONTAP. The recovery commands allow the VASA Provider to reload this metadata into its database.
