This section describes the use of the SnapMirror feature for basic data replication between the SnapMirror source and destination, and basic recovery operations.
Note
If your source volumes contain directories that are accessed by CIFS clients, ensure that those directories are in Unicode format before carrying out the SnapMirror replication of that volume. See Ensuring accessible destinations when using CIFS.
To complete a basic SnapMirror setup, complete the following steps.
| 1 |
Make sure you have purchased a SnapMirror license for both the source and destination systems. |
| 2 |
In both the source system and the destination system consoles, use the license add command to enable the SnapMirror license on the source and destination systems. license add snapmirror_license_code For more information see Entering license codes. |
| 3 |
On the source system console, use the options snapmirror.access command to specify the host names of systems that are allowed to copy data directly from the source system. For example: options snapmirror.access host=d_systemA For more information see How to specify destination systems on the source system. |
| 4 |
Through the Data ONTAP AdminHost, create or edit the /etc/snapmirror.conf file on the destination system to specify the volumes and qtrees to be copied and the schedule (minute hour day_of_month day_of_week or sync) on which the destination is updated. For example, the following entry specifies Snapshot mirroring from volume 0 of s_systemA to volume 1 of d_systemA at a maximum of 2,000 kilobits per second 15 minutes past every hour, Monday through Friday: s_systemA:vol0 d_systemA:vol1 kbs=2000,restart=always 15 * * 1,2,3,4,5 If you want to synchronously mirror volume 0 to volume 1, you use a command similar to the following: s_systemA:vol0 d_systemA:vol1 - sync For more information on schedule entries in the destination system's /etc/snapmirror.conf file, see Defining source and destination through snapmirror.conf and the na_snapmirror.conf(5) man page. |
| 5 |
In both the source system and destination system console, use the snapmirror on command to enable SnapMirror on the source and destination systems. For more information, see Enabling SnapMirror. |
| 6 |
Prepare the destination system appropriately, depending on whether you are setting up SnapMirror volume or qtree replication.
For more information, see the information about creating volumes in the volume management chapter of the Storage Management Guide; and see the information on restricting volumes in How to initialize a SnapMirror destination. |
| 7 |
In the destination system console, use the snapmirror initialize command to create an initial complete (baseline) copy of the source on the destination and start the mirroring process. SnapMirror volume replication exampleInvoking the following command line transfers a complete copy of the source volume (vol0 on systemA) to the destination volume (vol2 on systemB). The destination volume must be configured as restricted and read-only. snapmirror initialize -S systemA:vol0 systemB:vol2 SnapMirror qtree replication exampleInvoking the following command line creates a destination qtree (qtree4 on vol1on systemB) and transfers a complete copy of the qtree source (qtree4 on vol1 on systemA) to that destination qtree. The volume in which the destination qtree is created must be online and writable. snapmirror initialize -S systemA:/vol/vol1/qtree4 systemB:/vol/vol1/qtree4 After you invoke the snapmirror initialize command, the scheduled Snapshot mirroring that you specified in Step 4 will automatically update the destination volume or qtree at the specified times. See Initializing a SnapMirror destination for more information. |
| 8 |
In the event that the SnapMirror source volume or qtree is disabled, you can use the snapmirror break command to make the destination volume or qtree writable and able to provide continuous file and data service to the clients who are no longer able to access the disabled source system. For more information, see Converting a destination to a writable volume or qtree. |
If you have an asynchronous SnapMirror relationship and you want to convert it to a synchronous SnapMirror relationship, complete the following step.
If you are using Fibre Channel connections between the source system and the destination system, the systems must use 2352 (X1024) adapters. After configuring the Fibre Channel adapters, you can perform asynchronous and synchronous SnapMirror replication across the Fibre Channel connection. To configure the systems for Fibre Channel use, complete the following steps.
| 1 |
Install the Fibre Channel adapters in the source and destination systems. See the hardware and service guide for your storage system for installation instructions and the System Configuration Guide to ensure you install the adapter in the correct slot. |
| 2 |
Connect the systems to Fibre Channel switches. See the hardware and service guide for more information. |
| 3 |
On the console of each switch, configure the switch for a default configuration with no zoning and add long-distance Extended Fabric keys. See your switch documentation for configuration information. Note ExampleThe following Brocade switch commands might be used to configure a Brocade switch: switch_con> switchdisable switch_con> configdefault switch_con> fastboot |
| 4 | |
| 5 |
Configure the Fibre Channel adapter on each system by entering the following command at the console for each system: ifconfig qlXa ipaddr netmask 255.255.255.0 up a is either port a or port b (labeled on the adapter). ipaddr is the IP address of the adapter. Note ExampleThe following commands configure port a of two Fibre Channel adapters. The net address is 10.10.10.0. ifconfig ql3a 10.10.10.24 netmask 255.255.255.0 up On system B: ifconfig ql3a 10.10.20.24 netmask 255.255.255.0 up |
| 6 |
Ensure that the two systems can communcate by using the ping command. ExampleThe IP address on the destination system is 10.10.20.24. source> ping 10.10.20.24 10.10.20.24 is alive |
| 7 |
Follow the steps in Completing a basic SnapMirror setup to complete the SnapMirror setup. |
After configuring Fibre Channel adapters, you might see adapter reset messages similar to the following:
Sun Sep 7 20:30:00 PDT [system1: cf.nm.nicReset:warning]: Interconnect nic 2 is being reset
Sun Sep 7 20:30:03 PDT [system1: nic_mgr:info]: Saving reg dump for Qlogic VI Fibre Channel Adapter(2) to file /etc/ispfcvi_regdump.5
If you see an adapter reset message like this, check whether you have any of the problems listed in the following table and use the recommended solutions as needed.
Copyright © 1994-2005, Network Appliance, Inc. All rights
reserved.
Part No. 210-01081_B0
File: mirror7.htm
Last updated: 01-Dec-2005 16:36:03