跳转到主内容

NDB 备份间歇性失败,并显示错误 "Volume "xxxx" does not exist in Vserver "xxxx" 。原因:条目不存在

Views:
11
Visibility:
Public
Votes:
0
Category:
netapp-data-broker
Specialty:
snapx
Last Updated:

适用于

NetApp Data Broker ( NDB ) 1.0/1.0.1

问题

  • 在 NDB 备份期间,如果 API 因某些原因而出现故障,则在重试 API 时,指定的 Vserver 名称将不正确。
  • 这将导致错误 "Volume "xxxx" does not exist in Vserver "xxxx". Reason: entry doesn't exist."

例如Volume_A,卷 " " 位于 "SVM_A" 中,但在重试 API 时,错误地将其指定为 "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.

 

CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support