SnapMirror

y y

y y y y

y y y y y y y

This enables you replicate the data from volume or qtree to the volume or qtree. This requires a separate license. Modes of Snapmirror y Asynchronous mode :-replicates the snapshots are specified intervals y Synchronous mode:- replicates the snapshots as soon as they are written to the source y Semi-synchronous mode:-The destination volume lags behind the source volume by 10 Sec SnapMirror can be used either for Flex Volume and also Traditional Volume. How it works Files and options involved in snapmirror ( /etc/snapmirror.conf, snapmirror.access,/etc/snapmirror.allow) It takes the snapshot copy of the source volume and copies to the destination in the read only mode. Updates the changes in the destination in the incremental mode. As result you get an online read only volume or qtree. Application of snapmirror Disaster recovery = You can make the destination writable so clients can access the data. Disaster recovery testing = FlexClone technology in the destination without affecting the replication process Data restoration = you can reverse the destination and source volume or qtree and sync the data. Application testing = you can copy the data using the snapmirror so that source data is not disturbed. Load Balancing = you can copy the data using the snapmirror and distribute the load. Off - Loading the tape backup= you can take backup from the destination volume and offloading the source utilization. Access for remote users.

Synchronous SnapMirror
yIn this mode the data is written to the destination as soon as it is written to the sourcce filer yThe data's can synced either between the systems or between the system in the active/active cluster either via ip or fcp yWe require separate license apart from the snapmirror license for the synchronous transfer of data. yThis can be used only in the case of the volume not with the qtree's and that two the volume should of same type.As there are two types of volume they are Traditional volume and also FlexVol Volume. yThere are two types of synchronous modes y sync y semi-sync ( This is used for balancing between the sync and also asynchronous mode of transfer) yyou cannot set both sync and semi-sync relationship between filers of active/active configuration, and the definition has to be done in the /etc/snapmirror.conf file. ySync = The source acknowledges the client only after the write opertation is done at both the source and also destination and recovery point objective is almost 0 seconds. ySemi-sync = The source acknowledges the client write operation immediately after it is written in the source.The data is written to the destination with time lag of 10 sec. This implies the recovery point objective is 10 sec which means the data of only 10 sec would lost at the tiime recovery. Adv of it is that the performance compared to the sync option. yIf neither of the two option are not specified then the it is set to asynchronous.

the destination qtree should not be created its automatically created at the time initialization (snapmirror initialize).use_auto_resync on .volume. yRAID group size is 16 or fewer disk. yIn asynchronous mode the source tries to communicate the destination with the time interval of one minute.systemA:volA systemB:volB semi-sync yHow Sync Works:-Before the data is written to the disk the data's is written to the NVRAM and at the consistency point the data is transferred to the disk. . yIP needs to be resolvable in the both the ends (Source and destination).established then the source replicates the destination asynchronously to the destination.options snapmirror.enable on (This persist even after the reboot) Consideration for use of snapmirror Pre-requisites yNeed to enable the license at the filers where we are going to use the snapmirror. yThe transition is possible only in the case of latest common snapshot is available otherwise the need to break the snap(snapmirror break) and then resync it with (snapmirror resync). yAfter the connection is re.The default vaule of it is off. yFor QSM OnTap version should be more than 6. yTuning snapmirror :. Things to consider before growing aggregate with synchronous snapmirror destination volume. yThis can also be overcomed with the option replication.ySyntax :. In the case synchronous when the data's are written to the NVRAM the source sends the data to the destination NVRAM's and at the consistency point the source asks the destination to write the data to the disk and source also writes the data to the disk.If there is any network issues then the snapmirror goes into the asynchronous mode.Snapmirror follows the steps in the case network issues ysnapmirror sets the mode in the asynchronous mode. yAdd minimum of four disk. yIF YOU ARE UPGRADING THE FILER DESTINATION NEEDS TO BE DONE BEFORE SOURCE.2.If you use it for DR then both filer should be off same version. yThe destination filer for the snapmirror volume replication needs to be same version or the later one comparing to the source. yNew RAID group is created with atleast four disks. After this source waits for the acknowledgement from the destination before it starts the next write operation yHow it handles network issues :. ySnapmirror volume replication requires the destination volume to be in the restricted mode and needs to be created also. ySnapmirror then gradually transitions replication mode from the asynchronous to synchronous mode. yFor QSM .

Deduplication with volume snapmirror yIn the case deduplication.These are data object where the data is synchronized . yDon't use snapmirror release or snapmirror break in the destination less you don't require the incremental changes from the source. Destination qtree can be on the root that is /etc but cannot be /etc qtree. yDon't take the destination volume offline.The newely created snapshot is called NCS(Newely created snapshot copy).Incremental copy depends upon the NCS. yIn QSM the destination needs to be more than 5% more than the source qtree consumes. Source volume or qtree's :-These are data objects that are need to synchronized or replicated. Destination volume or qtree's:. yIn VSM the destination volume cannot be the root volume but the source volue can root volume. This can be done with the following options vol options vol_name convert_ucode on Deployment of snapMirror y y y It consists of source volume and qrees. The destination volume needs to be writable if we use QSM . yDestination needs to be more than the source or equal to that. The deduplication metadata is kept in the aggregate level outside of the volume. so metadata is not replicated along with the volume so in the detination the deduplication needs to be started using the sis start -s ( Without -s options only newly written data is scanned for the deduplication) Destination accessability when using CIFS with snapmirror yThe directories needs to be unicode format. and destination volume and qtree .Restrictions ySource volume needs to be online. yIf the source and destination are FlexVol Volume then there is no problem with the RAID configuation. Point of Caution while snapmirror yDo not delete the snapshot copies that the snapmirror creates in the source before copying to the destination.Normally users access these data's object and have read write access to the data's. yIn QSM. Recommenations of SnapMirror yThe schedule time of snapmirror and also snapshot should not happen at the same time. Destination volume or qtree are only read only.Then the snapshot wo uld fail saying in the log file that already a snapshot copy is available.

.e traditional and also FlexVol Volume.y y y The volumes can be used for both traditional and FlexVol Volumes. i. QSM 2. It supports different kind volumes. This supported only same kind of volume either traditional volume or FlexVol Volume. VSM 1.

SnapMirror Deployment variations y source to destination to tape variations .

Writable source is being replicated to the multiple read-only destination volumes. After the large base snapshot copy has been replicated then incremental snapshot copy can be carried out. y Cascading destination variables:.enable on . Between snapmirror on and snapmirror off command you need wait for 60 seconds for proper transfer of controls) To enable you can also use options snapmirror. SnapMirror commands y y Snapmirror on ( Use to enable the snapmirror. y Migration of traditional volume to FlexVol Volume:-Only QSM can be used in this case because the VSM does not support the replication volume on different volume types.y source to tape to destination :. It is supported only for VSM not for QSM.This case is used if the initial data's to be transferred is off large size.

allow)(If both options and /etc/snapmirror.volume. Other options /etc/snapmirror.volume. and allowing the active snapmirror transfer to finish and temporarily preventing the new transfers).2.conf ( They are used to specify the relationship between the source and the destination along with the following 1.enable on|off ( Default is off) Snapmirror. snapmirror status (view the status of the snapmirror) snapmirror update (Manually updating the snapmirror destination ) snapmirror quiesce (Stabilize the contents of the destination volume before snapshot is taken.volume.logical.3.x limit and previous is set as 7. Type of relationship (single.log. Snapmirror resume (Resume the normal transfer after quiesce).x files (Default on) Replication.y y y y y y y y y y y y y y vol create and vol restrict (To create destination volume snapmirror) snapmirror initialize (Used to start the initial transfer of snapshot(Baseline copy) from the source to destination . multipath or failover) 3. and continue the same on subsequent tapes). Snapmirror abort (Stopping the active snapmirror) Snapmirror break (Used to break the relationship between the source and the destination volume and convert the volume in writable volume or qtree) Snapmirror resync (Reestablish the relationship between the source and destination volume .reserved_transfers n (specifies the number of reserved transfers for snapvault and snapmirror qtrees where n is the number of times and default is 0).enable on|off(Whether the snapmirror activity is being logged /etc/log/snapmirror.transfer_limits {current|previous}(Specifies the maximum number of transfers the volume snapmirror can run concurrently)(Default is current)(Current is set as 7. Snapmirror retrive and snapmirror use (Initial or restore the volume from the local tape) Snapmirror destination (Used in the case of cascading the snapmirror destination ) Snapmirror options y y y y y y y y Snapmirro.logical.use_auto_resync on|off (specifies automatic re-synchronisation for synchronous snapmirror relationship) (Default off) Replication.x limit and previous is set as 7. Snapmirror update schedule for relationship 2.enable off Snapmirror store and snapmirror use(Copy the volume to the local tape.x limit) Replication.2. Replication.access host=list(list is hostnames separated by comma)(Default = legacy this means the access depends upon the list of hostnames available in /etc/snapmirror.transfer_limits {current|previous}(Specifies the maximum number of transfers the qtree snapmirror and snapvault can run concurrently)(Default is current)(Current is set as 7.allow are used then options takes precedence) Snapmirror.3.allow ( Specifies the snapmirror destination that are allowed to copy from the system) . This command is generally issued after the snapmirror break so that we avoid the initial transfer which is the baseline copy) Snapmirror release (The snapshot copies are deleted) Snapmirror off (Turn off the snapmirror functionality) alternatively options snapmirror.x limit) Snapmirror files:y y /etc/snapmirror.reserved_transfers n (Specifies the number of reserved transfers for the snapmirror volumes and n is the number of times and it depends upon the system model default is 0) Replication.

d_systemA>snapmirror initialize S systemA:vol0 systemB:vol2 QSM:. here the first synchronous relationship is supported only in the 7.2.0 snapmirror.1) /etc/hosts( Used for resolving the host names) Setting up a basic snapmirror operation:y y y License need to be enabled in the source and also destination filer.3. Snapmirror source is binded to the 10566 port number.4.1. Data replication:y y Destination data can be replicated to the other location which means it acts as the source for some filers.access host=d_systemA In the destination /etc/snapmirror. .restart=always 15 * * 1.allow If the source volume contains the directories that are being accessed by clients then the volume needs to be changed to the Unicode format before the replication. So ports between 10565 to 10569 needs to opened. Need to specify the destination systems name on the source filer in the /etc/snapmirror. VSM :. Destination listens on the 10565.2 and 7. STEPS:y y y y y y license add snapmirror_license_code s_systemA>options snapmirror. These are two hop cascading scenario s y These are three hop cascading scenario s.d_systemA>snapmirror initialize S systemA:/vol0/vol1/qtree4 systemB:/vol2/vol1/qtree4 Firewall usage with snapmirror:y y y They use socket/bind/listen/accept sequence on the TCP socket. Synchronous snapmirror requires extra one more port which is 10569.1 releases.5 and s_systemA:vol0 d_systemA:vol1 sync In both source and destination the snapmirror on needs to be given.10567.y y /etc/log/snapmirror ( Latest the snapmirror and the older ones are snapmirror.allow s_systemA:vol0 d_systemA:vol1 kbs=200. This is called the cascading.2.10578.

y y y In cascading you use the snapmirror destinations commands to check the number destination for a particular volume snapmirror destinations also displays commands related to the vol clone and also dump c ommand #snapmirror destinations s [volume_name] ( -s lists the number of snapshot copies that are available for the volume) Snapmirror source to tape to destination source y y The baseline copy is transferred via tape and then incremental happens via snapshot copies i.e snapmirror. Snapmirror update or scheduling for the snapmirror schedule in the /etc/snapmirror. Steps followed 1. Snapmirror release ( For releasing the relationship b/w the tape and the source) j Snapmirror status j Snapmirror release vol1 snapmirror_tape .1400*10 vol3 nrst0a. Snapmirror store and snapmirror use ( On the source system) j Snapmirror retrieve g vol_name ( This returns value as 7000*10 where 10 means number of disks and 7000 means the blocks)(Provide the command both in the source and also destination volume its better it matches if it does not please note it down in both the systems) j Snapmirror store g [disk_geomen] vol_name dest_tapedrives j Eg: snapmirror store g 7000*10. Snapmirror retrieve and snapmirror use j Snapmirror retrieve dest_volume tape_drive j Snapmirror use volume tape_list(Tape device from where you are restoring) 4.cong j Snapmirror update [-k n] S source_system:source_volume destination_system:destination_volume( k n is similar to kbs) 5. Transport the tapes physically 3.rstla j Snapmirror use dest_tapedrives(tape drives) tape_drive(This is drive holding the new tape) 2.

After the transfer is completed it brings the volume in the read only mode and also online. In QSM files are available in the source and also destination. In QSM . During the initial transfer of data the volume is marked invalid while executing the vol status command and it becomes valid and online after the initial transfer.Initializing the SnapMirror destination y y y y y y y y y Snapmirror initialize used for intial transfer of information between source and the destination. systemB>snapmirror initialize S systemA:vol0 systemB:vol2 systemB>snapmirror initialize S systemA:/vol/vol1/qtree4 systemB:/vol/vol2/Destn_qtree Space Guarantee on volume snapmirror destinations:y You can reserve space on the aggregate for the destination volume. we don t create the qtree and initialize command itself creates it. The destination volume is already created and in restricted mode. Destination qtree quota should be within the range of data available in the source. In the following we are going to sync the data between the volume and the qtree Snapmirror initialize S source_system:/vol/vol3/. This can be viewed with the vol options vol_name guarantee {none | file | volume } and the default is the guarantee=volume. so transfer happens with the help of the already created snapshot s and no other new snapshot s are created while transferring. the language of the volumes should be same. Initializing a destination with the non-qtree data:y y y y Non-qtree data are data s that are not available within the qtree.conf)  -c snapshot_name creates the snapshot copy in the destination system  -s snapshot_name specifies the snapshot name in the source system. snapshot in the destination shows busy via command snap list until the initial transfer.  -S source_system:source_volume|source qtree_path ( The source should match the one in the /etc/snapmirror. In VSM files and snapshot copies are available both in the source and also destination.dest_system:/vol/vol2/non_qtree_data (Here (-) represents the non-qtree data and another important thing is that the qtree shouldn t be available before) Vice versa is not possible After running the snapmirror quiesce and snapmirror break on the destination. After Initialization. you can resume again by providing the snapmirror resync How does initialize command works (On volumes and Qtree):y y y y Snapmirror initialize copies the entire volume to the destination by creating the snapshot of the entire volume. . Initialization to and from tapes :. This is called initializing the destination.snapmirror store and snapmirror retrieve but only for volumes not for qtree s The destination volume need to be in the restricted mode using the vol restrict vol_name Snapmirror initialize [options] [dest_system:] {dest_volume|qtree_path} Options  -k n = Maximum transfer speed. Avoid renaming of the volume or qtree after relationship. In QSM. The volume where you want it should be online.

This makes the file system to be equal on the systems Maximum concurrent operations without Nearstone operations:- Maximum concurrent with Nearstone replications:- . In QSM qtree When we issue the initialize command snapmirror sets the vol options fs_size_fixed on.y y To check initialization . In VSM snapmirror status .

You can specify upto 254 qtree s in a specific volume. In the case on the non-qtree data the syntax would be y /vol/vol_name/. Maximum of 1024 entries can be there in the /etc/snapmirror.conf in depth:y y y You can create a centralized snapmirror. The system would ignore the entries pertaining to the other systems. y y y The destination qtree should not be created and the entire path of the qtree needs to be provided in it.allow file only when there is no active transfer of files for the source and destination relationship.conf. It would take 2 minutes to take effect if the snapmirror is enabled or else it would take once its snapmirror is enabled. In the case of active/active configurations the limit has to be shared between the both the systems.Snapmirror. You can edit the snapmirror.allow file for the site and copy it to the all the systems.= Can only be source not the destination .

.specifies the default parameters j Kbs is the Maximum transfer speed j Restart={Never(starts from the beginning never minds where it has been interrupted)|always(starts from where it has been interrupted)|defaults( same as always)} j Cksum={none|crc32c|crc32c_header_only(default)} j Visibility_interval={xs|xm|xh}determines the time taken to create the automatic snapshot in the source volume this is used in synchronous or semi-synchronous replication(Default is 30 seconds) j Wsize=size(This is the TCP window size represented in bytes) j Compression=enable( This is used only in asynchronous VSM) j Connection_mode={inet6|inet|unspec}(This specifies the type of connection. 0-59/5 for every five minutes y Turning of the schedules can be done by either deleting the entire line or by commenting out the line. Fibre Channel or Both.never j Update between 8-17 .y Parameters in the arguments j . There are two modes available  Multiplexing Mode  Fail Over Mode Steps in implementing the Multipath . There are different ways of connecting the relationship Ethernet.  Using different subnets for different routes. This does not prevent you from manual updates y Manual updates y y Snapmirror update system:volA Snapmirror update s source_snap c destn_snap S systemA:VolA systemB:/vol/vol2/userbak SnapMirror over Multiple Path :y y y y You might have more than one physical path s between the snapmirror relationships. There are two types they are  Static routes for different routes with different IP. * is all possible values. default is unspec) y Schedule parameters j Minute(0-59) hour(0-23) dayofmonth(1-31) dayofweek(0(Sunday) to 6(saturaday)) j Multiple values are separated via comma.

* * * * To view compression ratio snapmirror status l dst_vol Snapmirror status l(Long format of output) q(displays volumes or qtree which are quiesced t (active qtree s or volume) Moving Snapmirror sources:y y Volume snapmirror transfer s all the snapshot copies as the part of the snapmirro replication Qtree SnapMirror.3.conf file of the destination system .Compression for snapmirror relationship:y y y y y This is supported only in the case of asynchronous volume snapmirror.e DataOnTap It can be enabled for both the incremental and also initial transfers and needs to be enabled on per relationship basis. Connection_name=mutli(src_system. Snapmirror destination version should be above 7. source and destination have only one snapmirror in common.dest_system) Connection_name:src_vol dst_system:dst_volume compression=enable .2 i. Steps y Now make the old source readonly Change the /etc/snapmirror.

We need to create the snapshot copy and move in onto the destination and the also new source. This is unlike the VSM where every snapshot needs to be copied to the destination DataOntap on the destination should be the same of the source or the later one .Moving Qtree SnapMirror sources :y y In QSM.

Edit the /etc/snapmirror.conf on the destination Issue the following on the destination system Migrating data between the volumes using the snapmirror:y y y Snapmirror migrate source_system:src_vol dst_system:dst_vol Quota can be enabled by quota on vol_name and the file related to quota are /etc/quotas To make snapmirror break permanent issue the following command snapmirror release and to re-sync it please provide snapmirror resync Resizing a snapmirror source and destination volume pair:y y y y Vol status vol_name v Vol status vol_name b Vol size vol_name size Vol options vol_name fs_size_fixed on .

Sign up to vote on this title
UsefulNot useful