Skip to main content

NetApp wins prestigious Coveo Relevance Pinnacle Award. Learn more!

NetApp Knowledge Base

MetroCluster Vservers can be out of sync because of SnapMirror\SnapVault Policy errors

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

Applies to

  • MetroCluster
  • SnapMirror
  • SnapVault

Issue

  • MetroCluster Vservers can fail to sync because of Snapmirror\SnapVault Policy errors.
  • The offending policy will be named in the "MetroCluster vserver show" command output.

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

Scan to view the article on your device