Professional Documents
Culture Documents
S
napmirror works at Volume level or Qtree level. Snapmirror is mainly used for di
saster recovery and replication.
Snapmirrror needs a source and destination filer. (When source and destination a
re the same filer, the snapmirror happens on local filer itself. This is when y
ou have to replicate volumes inside a filer. If you need DR capabilities of a vo
lume inside a filer, you have to try syncmirror ).
Synchronous SnapMirror is a SnapMirror feature in which the data on one system i
s replicated on another system at, or near, the same time it is written to the f
irst system. Synchronous SnapMirror synchronously replicates data between single
or clustered storage systems situated at remote sites using either an IP or a F
ibre Channel connection. Before Data ONTAP saves data to disk, it collects writt
en data in NVRAM. Then, at a point in time called a consistency point, it sends
the data to disk. When the Synchronous SnapMirror feature is enabled, the sourc
e system forwards data to the destination system as it is written in NVRAM. Then
, at the consistency point, the source system sends its data to disk and tells t
he destination system to also send its data to disk.
This guides you quickly through the Snapmirror setup and commands.
1) Enable Snapmirror on source and destination filer
source-filer> options snapmirror.enable
snapmirror.enable
on
source-filer>
source-filer> options snapmirror.access
snapmirror.access
legacy
source-filer>
1
2
3
4
5
6
source-filer> options snapmirror.enable
snapmirror.enable
on
source-filer>
source-filer> options snapmirror.access
snapmirror.access
legacy
source-filer>
2) Snapmirror Access
Make sure destination filer has snapmirror access to the source filer. The snapm
irror filer s name or IP address should be in /etc/snapmirror.allow. Use wrfile to
add entries to /etc/snapmirror.allow.
source-filer> rdfile /etc/snapmirror.allow
destination-filer
destination-filer2
source-filer>
1
2
3
4
Transfer started.
Monitor progress with 'snapmirror status' or the snapmirror log.
1
2
3
destination-filer> snapmirror initialize -S source-filer:/vol/demo1/qtree des
tination-filer:/vol/demo1/qtree
Transfer started.
Monitor progress with 'snapmirror status' or the snapmirror log.
4) Monitoring the status : Snapmirror data transfer status can be monitored eith
er from source or destination filer. Use snapmirror status to check the status.
destination-filer> snapmirror status
Snapmirror is on.
Source
Destination
Lag Status
source-filer:demo_source
destination-filer:demo_destination
ed - Transferring (1690 MB done)
source-filer:/vol/demo1/qtree destination-filer:/vol/demo1/qtree
ed - Transferring (32 MB done)
destination-filer>
1
2
3
4
5
6
destination-filer> snapmirror status
Snapmirror is on.
Source
Destination
Lag Status
source-filer:demo_source
destination-filer:demo_destination
ed - Transferring (1690 MB done)
source-filer:/vol/demo1/qtree destination-filer:/vol/demo1/qtree
ed - Transferring (32 MB done)
destination-filer>
State
Uninitializ
Uninitializ
State
Uninitializ
Uninitializ
5) Snapmirror schedule : This is the schedule used by the destination filer for
updating the mirror. It informs the SnapMirror scheduler when transfers will be
initiated. The schedule field can either contain the word sync to specify synchr
onous mirroring or a cron-style specification of when to update the mirror. The
cronstyle schedule contains four space-separated fields.
If you want to sync the data on a scheduled frequency, you can set that in desti
nation filer s /etc/snapmirror.conf . The time settings are similar to Unix cron.
You can set a synchronous snapmirror schedule in /etc/snapmirror.conf by adding s
ync instead of the cron style frequency.
destination-filer> rdfile /etc/snapmirror.conf
source-filer:demo_source
destination-filer:demo_destination - 0 * * * #
This syncs every hour
source-filer:/vol/demo1/qtree destination-filer:/vol/demo1/qtree - 0 21 * * #
This syncs every 9:00 pm
destination-filer>
1
2
3
4
destination-filer> rdfile /etc/snapmirror.conf
source-filer:demo_source
destination-filer:demo_destination - 0 * * * #
This syncs every hour
source-filer:/vol/demo1/qtree destination-filer:/vol/demo1/qtree - 0 21 * * #
This syncs every 9:00 pm
destination-filer>
6) Other Snapmirror commands
To
To
To
To
Snapmirror do provide multipath support. More than one physical path between a s
ource and a destination system might be desired for a mirror relationship. Multi
path support allows SnapMirror traffic to be load balanced between these paths a
nd provides for failover in the event of a network outage.