Skip to main content
NetApp Knowledge Base

NDB backup fails intermittently with error "Volume "xxxx" does not exist in Vserver "xxxx". Reason: entry doesn't exist."

  1. Last updated
  2. Save as PDF
Views:
348
Visibility:
Public
Votes:
1
Category:
snapcenter
Specialty:
snapx
Last Updated:

Applies to

NetApp Data Broker (NDB) 1.0/1.0.1

Issue

  • During NDB backup, in case of API failure due to some reasons, when the API is retried, incorrect vserver name will be specified.
  • This will cause the error, "Volume "xxxx" does not exist in Vserver "xxxx". Reason: entry doesn't exist."

For example, Volume "Volume_A" exists in "SVM_A", but when retrying the API, it's wrongly specified as "SVM_B".

YYYY-MM-DD HH:MM:SS.XXX +09:00 [ERR] API exception
YYYY-MM-DD HH:MM:SS.XXX +09:00 [ERR] Failed to run a command New-NcSnapshotMulti
YYYY-MM-DD HH:MM:SS.XXX +09:00 [DBG] ex.InnerException.InnerException.Message : An error occurred while sending the request. Unable to read data from the transport connection: Broken pipe.
...
YYYY-MM-DD HH:MM:SS.XXX +09:00 [ERR] API exception
YYYY-MM-DD HH:MM:SS.XXX +09:00 [ERR] Failed to run a command New-NcSnapshotMulti
YYYY-MM-DD HH:MM:SS.XXX +09:00 [DBG] ex.InnerException.Message : Volume "Volume_A" does not exist in Vserver "SVM_B". Reason: entry doesn't exist.
YYYY-MM-DD HH:MM:SS.XXX +09:00 [DBG] No retry condition match found or max retry reached. Throwing error Volume "Volume_A" does not exist in Vserver "SVM_B". Reason: entry doesn't exist.

 

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.