Skip to main content
NetApp Knowledge Base

VASA Provider: How to recover when VASA Provider database is corrupt or lost

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

Applies to

  • ONTAP Tools for VMware vSphere (OTV) 9.6 and later
  • ONTAP VASA Provider

Description

This article covers the following scenarios where:

  • VASA Provider (VP) database has been wiped out through administrative action when it should not have been (i.e. reset via the OTV Maintenance Console)
  • The VASA Provider database has been corrupted. 

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

Note: This procedure is to only be used when the original OTV appliance is still available.  If you have provisioned a new, replacement OTV appliance, please use How to recover when VASA Provider has been lost or is inaccessible

 

 

 

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.