跳转到主内容

SnapCenter插件:备份找不到SnapMirror或SnapVault关系

Views:
28
Visibility:
Public
Votes:
0
Category:
snapcenter
Specialty:
snapx
Last Updated:

适用场景

  • SnapCenter服务器(SC)
  • 适用于SQL的SnapCenter插件(SCSQL)
  • 适用于Exchange的SnapCenter插件(SCE)
  • 适用于VMware vSphere的SnapCenter插件(SCV)
  • 适用于Oracle的SnapCenter插件

问题描述

  • SnapCenter备份找不到ONTAP中存在的SnapMirror或SnapVault关系。
  • 以下错误出现在C:\Program Files\NetApp\SnapCenter\SMCore\log\SMCore_###.log文件中。

ERROR SMCore_#### PID=[####] TID=[##] ErrorCode (-1), ErrorMessage (Unable to find SnapMirror destination(s). Error: No SnapMirror relationships were found. Resolution: Please make sure that secondary storage systems are registered and host can resolve them correctly.)

2025-03-05T14:58:47.7434705-05:00 DEBUG SMCore_577561 PID=[6316] TID=[51] Invoking Connect-NcController ...
2025-03-05T14:59:08.7751410-05:00 DEBUG SMCore_577561 PID=[6316] TID=[51] ex.Message : The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: API invoke failed:A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. [SVM IP]:443 (SVM IP:443)
2025-03-05T14:59:08.7753814-05:00 DEBUG SMCore_577561 PID=[6316] TID=[51] --StorageConnection::InitializeONTAP
2025-03-05T14:59:08.7754009-05:00 DEBUG SMCore_577561 PID=[6316] TID=[51] InitializeONTAP() throw exception: API invoke failed:A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. [::ffff:10.81.252.125]:443 (10.81.252.125:443)
2025-03-05T14:59:08.7755265-05:00 ERROR SMCore_577561 PID=[6316] TID=[51]
Message : API invoke failed:A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. [::ffff:SVM IP]:443 (SVM IP:443)
Source : SnapDrive.Nsf.Core.Storage
StackTrace : at SnapDrive.Nsf.Core.Storage.StorageConnection.Initialize(SDStorageSystemId storageSystemId)
2025-03-05T14:59:08.7756772-05:00 DEBUG SMCore_577561 PID=[6316] TID=[51] --StorageConnection::Initialize
2025-03-05T14:59:08.7757242-05:00 DEBUG SMCore_577561 PID=[6316] TID=[51] --StorageConnection::GetStorageConnection
2025-03-05T14:59:08.7758496-05:00 DEBUG SMCore_577561 PID=[6316] TID=[51] --ResourcePool`2::GetResource
2025-03-05T14:59:08.7759047-05:00 DEBUG SMCore_577561 PID=[6316] TID=[51] --SnapMirrorManager::GetSnapMirrorInfo
2025-03-05T14:59:08.7759116-05:00 ERROR SMCore_577561 PID=[6316] TID=[51] Failed to get SnapMirror relationships [StorageSystem: Destination_SVM _Name as destination]

 

  • 在选择控制阀ProtectionService.logJob-<JOB_ID>.log 中可以看到相同的故障。

[ERR]无法运行命令NetApp.DataProtection.Storage.CommandAPI.ConnectNcController、异常:必须指定HTTP或HTTPS

 Either HTTP or HTTPS must be specified
..
[ERR] ErrorCode (-1), ErrorMessage (Unable to find SnapMirror destination(s). Error: No SnapMirror relationships were found. Resolution: Please make sure that secondary storage systems are registered and host can resolve them correctly.)
[ERR] ErrorCode (-1), ErrorMessage (Unable to find SnapMirror destination for the source volume(s) <sourceSVM:sourceVolume>)

  • 选择控制阀作业详细信息显示错误。

SnapVault update failed for the relationship [<relationship_path>] with error: Snapshot copy '<snapshot_name>' not found on the SnapVault destination <destination-path>

或 

Error: No SnapVault destination found for <SVMname> : <volumename>

 

 

 

 

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.