2015

Volumes, SnapMirror Targets, LIFs, DNS, Shares, DFS
RUSS WITT & RAKESH KASARANENI

WILLIAMS LPZ | 525 Central Park Drive, Oklahoma City, Oklahoma 73105

............................................. This document shows an example of the elements of a NetApp Windows share on a volume replicated for Disaster Recovery......................................................................................................... 3 DFS ................... 2 DNS................................................................................... ........................................................................................ 2 LIFs ............................... 3 Windows View of the Share with the “net view” command........................................... ........................................................................................................................................................................................................................................................................................................................ 2 Shares ............................................................................................................................................................................................................................................................................................................................ 1 Volumes ......................................................................................................................................... 2 SnapMirror Targets ................................................................................................................ Table of Contents About this Quick Reference..................................... 3 NetApp View of the Share..........About this Quick Reference.................................................................. 4 ...................................................................

------.---.---. Z:###BOT_TEXT###gt;nslookup 10.---------.williams.---------.net Address: 10.-----------.-----------.32.--------.com Address: 10.150 Server: okokcn1.14TB 67% SnapMirror Targets Production Windows Shares are replicated to the DR environment.150/22 tulntapcl01-06 a0a-817 true DNS The LIF IP is in DNS.-------- okcsvm_prod:cifs_app_root DP tulsvm_prod:vol_cifs_app_root_snapmirror Snapmirrored Idle . tulntapcl01::> snapmirror show -destination-volume vol_cifs_app_root_snapmirror Progress Source Destination Mirror Relationship Total Last Path Type Path State Status Progress Healthy Updated ----------.----- tulsvm_prod vol_cifs_app_root_snapmirror tul06_silver_aggr01 online DP 3.90. true - LIFs The Share has a dedicated LIF tulntapcl01::> net int show *cifs_app* (network interface show) Logical Status Network Current Current Is Vserver Interface Admin/Oper Address/Mask Node Port Home ----------.32. The following example shows a SnapMirror replication of the Application Share from Production to the DR target NetApp Cluster.250.32.---------.90.50TB 1.---------. ------------.-----------.-------------.------.150 .------.15 Name: cifs_app_root_dr.accessmidstream.---- tulsvm_prod cifs_app_root_dr up/up 10.---------.-----------------.Volumes tulntapcl01::> volume show *vol_cifs_app* Vserver Volume Aggregate State Type Size Available Used% --------.91.90. Note the source cluster and volume and the destination cluster and volume.

Verifying the DR Share is ready to put into DFS If you can do a dir command on the share it is ready to be put into DFS. ---------. All shares on the Storage Virtual machine are visible from any SVM LIF that has the CIFS protocol running. 03/02/2015 02:33 PM <DIR> . N:###BOT_TEXT###gt;dir \cifs_app_root_dr\vol_cifs_app_root_snapmirror Volume in drive \cifs_app_root_dr\vol_cifs_app_root_snapmirror has no label.. You cannot write files to it but you can read with the same permissions required in the original share.Break Mirror and repoint DFS to use vol_cifs_app_root_snapmirror Disk CIFS Share for Snapmirror of app root directory vol_cifs_department_root_snapmirror Disk CIFS Share for Snapmirror of department root directory The command completed successfully. 12/16/2014 12:11 PM <DIR> esuite 05/07/2013 11:35 AM <DIR> gis 06/12/2013 02:27 PM <DIR> kmi 05/14/2014 01:38 PM <DIR> app_flairdocs 09/02/2015 10:12 AM <DIR> hyperion 10/29/2014 11:20 AM <DIR> oracle 06/13/2013 10:21 AM <DIR> promax 11/12/2013 10:06 AM <DIR> exchange 05/14/2013 02:00 PM <DIR> zoom . Our Share is “Hidden” using the windows trailing $ convention. Note that this share is Read Only as it is an active replication target (SnapMirror).----------- tulsvm_prod vol_cifs_app_ /vol/vol_cifs_ oplocks CIFS Everyone / Full Control root_ app_root_ browsable Share snapmirror snapmirror changenotify for Snapmirr or of app root director y Windows View of the Share with the “net view” command.. ------------.----------------. Volume Serial Number is 8000-0B37 Directory of \cifs_app_root_dr\vol_cifs_app_root_snapmirror 03/02/2015 02:33 PM <DIR> . The list is truncated with … here for brevity.-------.Shares NetApp View of the Share tulntapcl01::> cifs share show *cifs_app_root* Vserver Share Path Properties Comment ACL -------------. Note the /all syntax to show hidden shares. Z:###BOT_TEXT###gt;net view \cifs_app_root_dr /all Shared resources at \cifs_app_root_dr (null) Share name Type Used as Comment ------------------------------------------------------------------------------- tulsa_backup3$ Disk CIFS CommVault Backup Target vfcitrix$ Disk CIFS SnapMirror of Citrix VDisks CIFS Share for DR .

rather they are fronted by the Distributed File Services (DFS) name space.197.251.txt) to the share as it is a replication Mirror. N:###BOT_TEXT###gt;dir \cifs_app_root_dr\vol_cifs_app_root_snapmirror >\cifs_app_root_dr\vol_cifs_app_root_snapmirror\dir. When you create a new DFS folder target you will be asked if you want Windows to replicate the contents. DFS allows for changing the back end storage names without disrupting the mount paths on thousands of clients. To use the DR share in a DR. Break the SnapMirror to make it writeable. We do not use this Windows feature for this use case. The DR DFS Folder Target should be “Disabled” so that the traffic goes to the Production share. . We use DFS only in a DR or maintenance event to re-point clients to the DR Share till the production share is available again. Clients mount the DFS name instead of the NetApp Share.120 bytes free Notice that you cannot write (>###BOT_TEXT###lt;path>\dir.txt Access is denied. DFS Clients do not connect directly to the NetApp shares.384.09/10/2014 01:43 PM <DIR> InSight 09/08/2015 05:26 AM <DIR> FlowCalDownload 10/17/2013 03:42 PM <DIR> employee 03/21/2014 01:26 PM <DIR> maximo 03/04/2015 02:21 PM <DIR> TeamMate 11/06/2014 01:21 PM <DIR> sccm 03/06/2015 01:08 PM <DIR> flowcal 08/20/2015 10:44 AM <DIR> DataSplice 0 File(s) 0 bytes 19 Dir(s) 1. break the SnapMirror and switch the “Target” in DFS to the URI that includes the name or IP address of the LIF \cifs_app_root_dr plus the name of the share \vol_cifs_app_root_snapmirror.