Skip to main content
NetApp Knowledge Base

VASA Provider: How to recover when VASA Provider has been lost/is inaccessible

  1. Last updated
    Jun 12, 2025
  2. Save as PDF
Views:
862
Visibility:
Public
Votes:
0
Category:
netapp-vasa-provider
Specialty:
virt
Last Updated:
6/12/2025, 1:12:40 PM

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

 

 

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.