The /etc/snapmirror.conf file defines the relationship between the source and the destination, the schedule used by the destination to copy data, and the arguments that control SnapMirror when copying data. This file resides on the destination filer.
You can create a single /etc/snapmirror.conf file for your site and copy it to all the filers that use SnapMirror. The /etc/snapmirror.conf file can contain entries pertaining to other filers. For example, the /etc/snapmirror.conf file on filerB can contain an entry for copying a volume from filerC to filerD. When filerB reads the /etc/snapmirror.conf file, it ignores the entries for other filers. Each time the file is read, a warning message is displayed for each line that is ignored.
If SnapMirror is enabled, changes to the /etc/snapmirror.conf file take effect within two minutes. If SnapMirror is not enabled, changes to the /etc/snapmirror.conf file take effect immediately after you enter the snapmirror on command to enable SnapMirror.
To create or edit the /etc/snapmirror.conf file, complete the following steps.
| 1 | If it does not already exist, use a text editor to create a file called snapmirror.conf in the /etc directory on the root volume of the destination filer. |
| 2 | If you want to add comments to the /etc/snapmirror.conf file, precede the comment with a pound sign (#). Example# Replicating from filerA |
| 3 | For each destination volume or qtree that is to be located on this filer, type an entry specifying the source, destination, characteristics and schedule of the data transfer on one line using the following syntax: source_filer:{source_volume | /vol/volume_name/qtree_name}
dest_filer:{dest_volume | /vol/volume_name/qtree_name}
arguments schedule
For a full description of the snapmirror.conf file entry syntax see snapmirror.conf file entry syntax. Note Note If you want to combine all non-qtree data in a volume into a qtree to use as a SnapMirror source, use this syntax: source_filer:/vol/source_volume/- dest_filer:/vol/dest_volume/qtree_name The dash (-) character indicates all non-qtree data in the specified volume. Note |
| 4 |
The syntax for entries in the snapmirror.conf file is as follows:
src_filer:/vol/src_vol/[src_qtree]
dest_filer:/vol/dest_vol[/dest_qtree] [kbs=kbs],
[restart={never|always}] [sched]
The parameters in the entries are:
Suppose you create a private network between filerA and filerB. In the /etc/hosts file on filerA, you give the host name for the interface as filerA-e0, and you ensure that filerA-e0 is also in the /etc/hosts file on filerB, the destination filer. You want to copy vol0 of filerA to vol1 of filerB over the private network every Monday, Wednesday, and Friday at 11 p.m. You also want to use the default for the arguments field.
To copy the data over the private network every Monday, Wednesday, and Friday at 11 p.m., you would enter the following in the /etc/snapmirror.conf file:
filerA-e0:vol0 filerB:vol1 - 0 23 * 1,3,5
The following figure illustrates what the entry in each field in the example means.
The following line in an /etc/snapmirror.conf file sets the speed to 2000 kilobytes per second.
filerA:vol0 filerA:vol1 kbs=2000 15 * * 1,2,3,4,5
Note
The specified transfer speed might not be achievable because transfer speed is limited by factors such as network bandwidth.
The following line in an /etc/snapmirror.conf file sets the restart value to always.
filerA:vol0 filerA:vol1 kbs=2000,restart=always 15 * * 1,2,3,4,5
If you set the value of only one argument (kbs or restart), the other will use the default value. If you want to use the default argument for both values, enter a dash (-).
The following line in an /etc/snapmirror.conf file sets both arguments to the default value.
filerA:vol0 filerA:vol1 - 15 * * 1,2,3,4,5
If you want to schedule an update every afternoon at 1:00, 1:15, 1:30, 1:45, 5:00, 5:15, 5:30, 5:45, 7:00, 7:15, 7:30, and 7:45, you enter the following in the schedule field:
filerA:vol0 filerA:vol1 0,15,30,45 13,17,19 * *
Note
An update is started when the current time matches a value in all four fields. Be careful that a value in the day of the month field does not exclude a value in the day of the week field. For example, the following schedule would update the destination every afternoon at 1:00, 1:30, 3:00, 3:30, 5:00 and 5:30 but only when the first day of the month falls on a Monday.
filerA:vol0 filerA:vol1 0,30 13,15,17 1 1
Note
The schedule represents the goal of the SnapMirror feature. Factors that may prevent SnapMirror from updating every minute include resource limitations or network stability. If an update is in progress when another is scheduled to occur, SnapMirror will start another transfer as soon as the first is complete. However, if three updates pass while the current transfer is in progress, SnapMirror does only one more update; it does not go back and run updates that have been made obsolete by those scheduled later.
In SnapMirror, a retry is an automatic attempt to start the transfer process after an interruption, whether or not any data was successfully transferred. A restart is the resumption of a previous transfer process from a restart checkpoint.
If a transfer fails, because of network failure, for example, SnapMirror automatically retries the transfer. SnapMirror makes a restart checkpoint every five minutes during a transfer. If a restart checkpoint exists and conditions are right, SnapMirror restarts the previous transfer where it left off. If not, SnapMirror creates a new snapshot and starts a new transfer.
After a reboot, SnapMirror does not automatically retry a transfer that was interrupted, but the next scheduled or manual transfer restarts it at the restart checkpoint, if the checkpoint is still valid.
A restart can happen if all of the following conditions are present:
An initial transfer can be restarted but will not be retried automatically. To restart an initial transfer, you need to re-enter the snapmirror initialize command. Scheduled incremental updates automatically retry the transfer. A manual update issued from the command line is not retried automatically.
Copyright © 1994-2003, Network Appliance, Inc. All rights
reserved.
Part No. 210-00325
File: mirror7.htm
Last updated: 01/14/03 18:24:45