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

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.