Table of ContentsView in Frames

Monitoring the SVM disaster recovery relationship status

You can monitor the status of the SnapMirror relationship between the source and the destination SVMs to ensure that the updates are occurring based on the schedule.

About this task

SNMP is not supported for monitoring SnapMirror relationships between the source and destination SVMs.

Steps

  1. View the details of the SnapMirror relationship status by using the snapmirror show -instance command.
    Example
    destination_cluster::> snapmirror show -instance
    
                                Source Path: vs1:
                           Destination Path: dvs1:
                          Relationship Type: DP
                    Relationship Group Type: vserver
                        SnapMirror Schedule: -
                     SnapMirror Policy Type: async-mirror
                          SnapMirror Policy: DPDefault
                                  Mirror State: Snapmirrored
                        Relationship Status: Idle
                        ..
                        ..
                       Snapshot Checkpoint: -
                            Newest Snapshot: vserverdr.4eb1f1aa-e4ba-11e3-9b97-005056af93d7.2014-05-26_095857
                  Newest Snapshot Timestamp: 05/26 09:58:57
                          Exported Snapshot: vserverdr.4eb1f1aa-e4ba-11e3-9b97-005056af93d7.2014-05-26_095857
                Exported Snapshot Timestamp: 05/26 09:58:57
                                    Healthy: true
                                    Unhealthy Reason: -
                           ...
                           ...
                         Last Transfer Type: update
                         Last Transfer Error: -
                         Last Transfer From: vs1:
                Last Transfer End Timestamp: 05/26 10:05:24
                          ...
                          ...            
               Lag Time: 2:0:15           Identity Preserve Vserver DR: true
  2. If the Mirror State is Uninitialized, initiate the SnapMirror transfers again.
    The SnapMirror initialization or resynchronization operation might have failed because data replication failed at the volume level, configuration replication failed, or other such failures.
    • Complete the initialize operation by running the snapmirror initialize command again.
    • Complete the resynchronization operation by running the snapmirror resync command again.
  3. If the Healthy field is false and the Last Transfer Type is break, run the snapmirror break command again for the SVM disaster recovery relationship.
    Some volume-level SnapMirror relationships might have failed to break during the last SnapMirror break operation on the SVM disaster recovery relationship.
  4. Optional: After a cluster reboot, ensure that the source SVM is unlocked for any management operations.
    The source SVM is locked during the cluster reboot.
    1. Verify that the source SVM is locked by using the vserver show -fields config-lock command.
      Example
      source_cluster::> vserver show -fields config-lock
      
      vserver config-lock
      ------- -----------
      vs1     true
      
    2. If the source SVM is locked, then unlock it forcibly from the advanced privilege by using the vserver unlock command.
      Example
      source_cluster::> set advanced
      
      Warning: These advanced commands are potentially dangerous; use them only when directed to do so by NetApp personnel.
      Do you want to continue? {y|n}: y
      
      source_cluster::*> vserver unlock -vserver vs1 -force
      
      source_cluster::*> vserver show -fields config-lock
      
      vserver config-lock
      ------- -----------
      vs1		false