跳转到主内容

MetroCluster Vservers 可能由于 SnapMirror\SnapVault 策略错误而不同步

Views:
91
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
metrocluster
Last Updated:

适用于

  • MetroCluster
  • SnapMirror
  • SnapVault

问题

  • MetroCluster Vserver 可能因为 SnapMirror\SnapVault 策略错误而无法同步。
  • 违规策略将在"MetroCluster vserver show"命令输出中命名。

Cluster1::*> metrocluster vserver show

Cluster  : NetApp_Cluster
                              Vserver  : VSERVER1
                      Partner Vserver  : VSERVER1-mc
                  Configuration State  : degraded
                        Stream Status  : operation-failed
                    Corrective Action  : Resynchronize the configuration using "metrocluster vserver resync" command. Contact technical support for assistance if configuration-state does not change to healthy.
                           Failed Row : Table Name: snapmirror_policy_ui, Operation: get, Fields: VSERVER1-mc vault_7day vault vserver-admin - 8 normal false always false - sv_vault 14 false 0 - - - - - - - false - - - - - - - - - - - b7e70ff0-4b2e-11ea-9f9d-00a0989db67c - unlimited -
                         Failed Reason : Apply failed for Object: snapmirror_policy_ui Method: baseline. Reason: Volume name not found for volume Data Set ID 1073743309 and volume Master Set ID 3236753984. (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.