Professional Documents
Culture Documents
Purpose
Contents
CLI
In this scenario, FILERA is the source controller and FILERB is the destination
controller.
Note: The snapmirror resync will not succeed if either controller (source or
destination) cannot properly resolve the hostname of its respective source or
destination. If the entries do not exist in DNS, they can be added locally to the
controller by updating the /etc/hosts file.
Example /etc/hosts file
10.10.10.131 FILERA
10.10.20.131 FILERB
Show the status of the relationship
FILERB> snapmirror status
Snapmirror is on.
Source
Destination
State
Lag
Status
FILERA:src_vol
FILERB:dst_vol
Snapmirrored 00:10:38 Idle
Quiesce the mirror
FILERB> snapmirror quiesce dst_vol
Break the mirror
FILERB> snapmirror break dst_vol
Snapmirror is on.
Source
Destination
FILERA:src_vol
FILERB:dst_vol
State
Lag
Status
Broken-off
00:11:00 Idle
State
Lag
Status
Snapmirrored 00:00:03 Idle
Source
00:02:36 Idle
The same reverse replication can also be done from systems manager console and
below are the steps.
Quiesce and break the mirror when the resync has completed
Resync the original relationship