Monday, 23 April 2018

Lab Guide: Transitioning vFiler DR Relationship to SVM DR in ONTAP 9.0+

Indeed, Data ONTAP 7-Mode is still in use in the wild, but the date is soon approaching where it will go end of full support. The end of full support date for 7-Mode is 31st December 2020, which is 3 years on from the End of Availability (EOA) dates of the FAS2500/FAS80X0 platforms (these were the last platforms to ship with 7-Mode on); it then goes into Limited Support mode (no new maintenance patches will be released) until 31st December 2022 (see Data ONTAP 8.3 and earlier Software Version Support Policy and Support Plan Announcement For Systems operating Data ONTAP in 7-Mode.)

Lab Demonstration

My lab uses 7-Mode 8.2.3 controllers N7A & N7B, ONTAP 9.2 clusters C92A & C92B, and 7MTT 3.3.
This post goes through the following steps to demonstrate how to transition a vFiler DR relationship to an SVM DR relationship.

1) Create primary vFiler on N7A
2) Test CIFS access
3) Create vFiler DR on N7B
4) Prepare vFiler DR Environment for 7MTT
5) Create primary SVM on C92A
6) Create secondary SVM on C92B
7) Configure 7MTT
8) 7MTT Cutover
9) CIFS Server rename
10) SVM DR (SnapMirror for SVM) Configuration
11) Test CIFS access


Image: 7 to 7, 7 to C, and C to C relationships

Note: The below uses all CLI. It is also possible to do most of the below using the GUIs.

1) Create primary vFiler on N7A

The following commands create our primary vFiler with a root and a data volume; enable CIFS, and create a test CIFS share.


N7A> options rsh.enable on
N7A> options licensed_feature.multistore.enable on
N7A> options snapmirror.access host=*
N7A> snapmirror on
N7A> vol create vf1_root -s none aggr0 5g
N7A> vol create vf1_data -s none aggr0 5g
N7A> vfiler create vf1 -n -s default-ipspace -i 10.9.1.20 /vol/vf1_root
N7A> vfiler add vf1 /vol/vf1_data
N7A> vfiler allow vf1 proto=cifs
N7A> vfiler run vf1 setup


And answer the prompts:

Configure vfiler IP address 10.9.1.20? y
Interface to assign this address to: e0c
Netmask to use: 255.0.0.0
Do you want to run DNS resolver? y
Please enter DNS domain name: lab.priv
Please enter the IP address for first nameserver: 10.0.1.10
Do you want to run NIS client? n
Default password for root on vfiler vf1 is "".
New password:
Retype new password:


N7A> vfiler run vf1 options security.passwd.rules.history 0
N7A> vfiler run vf1 cifs setup


And answer the prompts:

Do you want to make the system visible via WINS? n
Selection (1-2)? 1 (for Multiprotocol filer)
The default name for this CIFS server is 'VF1'.
Would you like to change this name? n
Selection (1-4)? 1 (for Active Directory domain authentication)
What is the name of the Active Directory domain? lab.priv
Enter the name of the Windows user: Administrator@LAB.PRIV
Password for Administrator@LAB.PRIV:
Please choose where you would like this account to be created.
Selection? 1 (for CN=computers)
Do you want to create the VF1\administrator account? y
Enter the new password for VF1\administrator:
Retype the password:
Welcome to the LAB.PRIV (LAB) Active Directory(R) domain.


N7A> vfiler context vf1
vf1@N7A> qtree security /vol/vf1_data ntfs
vf1@N7A> cifs shares -add data /vol/vf1_data


2) Test CIFS access

With a Windows client - on the active directory domain used above - test you can map a drive to the share, and write/read data.


C:\Users\AUser> net use T: \\10.9.1.20\data
C:\Users\AUser> T:
T:> echo "TEST MESSAGE" > message.txt
T:\>more message.txt
"TEST MESSAGE"


3) Create vFiler DR on N7B

The following commands create the vFiler DR configuration.


N7B> options rsh.enable on
N7B> options licensed_feature.multistore.enable on
N7B> options snapmirror.access host=*
N7B> snapmirror on
N7B> vol create vf1_root -s none aggr0 5g
N7B> vol create vf1_data -s none aggr0 5g
N7B> vfiler dr configure vf1@N7A


And answer the prompts:

N7A's Administrative login: root
N7A's Administrative password:
Configuring SnapMirror to mirror vfiler vf1's storage units from remote filer N7A.
Upon Activation, configure vfiler IP address 10.9.1.20? y
Interface to assign this address to: e0c
Netmask to use: 255.0.0.0
Starting snapmirror initialize commands...
Volume 'vf1_root' is now restricted.
Volume 'vf1_data' is now restricted.
Upon activation, do you want the DR vfiler to use a different
set of DNS servers from the production vfiler? n
SnapMirror transfer initiated for vfiler storage units.


N7B> vfiler status
vfiler0   running
vf1       stopped, DR backup

N7B> snapmirror status
Snapmirror is on.
Source         Destination    State          Lag        Status
N7A:vf1_data   N7B:vf1_data   Snapmirrored   00:00:16   Idle
N7A:vf1_root   N7B:vf1_root   Snapmirrored   00:00:16   Idle


4) Prepare vFiler DR Environment for 7MTT

7MTT does not support transitioning vFiler DR, so we must delete the vFiler DR relationship, manually snapmirror the volumes, and we need a temporary vFiler to hold the data volumes.


N7B> vfiler dr delete vf1@N7A
Aborting data transfer for vfiler storage units....
DR configuration deleted for vfiler vf1.

N7B> snapmirror resync -S N7A:vf1_root N7B:vf1_root
N7B> snapmirror resync -S N7A:vf1_data N7B:vf1_data
N7B> rdfile /etc/snapmirror.conf
N7B> wrfile -a /etc/snapmirror.conf N7A:vf1_root N7B:vf1_root - 0-59/3***
N7B> wrfile -a /etc/snapmirror.conf N7A:vf1_data N7B:vf1_data - 0-59/3***
N7B> rdfile /etc/snapmirror.conf
N7B> vol create vf1_root_temp -s none aggr0 5g
N7B> vfiler create vf1_temp -n -s default-ipspace -i 169.254.254.254 /vol/vf1_root_temp
N7B> vfiler add vf1_temp /vol/vf1_data
N7B> vfiler allow vf1_temp proto=cifs


5) Create primary SVM on C92A

We create a primary SVM as destination for our primary vFiler, and configure CIFS (need a temporary CIFS server object so we can transition the CIFS configuration.)


C92A::> vserver create -vserver vf1 -rootvolume rootvol -aggregate data1 -rootvolume-security-style ntfs -language en.UTF-8
C92A::> net int create -vserver vf1 -lif data -role data -data-protocol cifs -home-node C92A-01 -home-port e0c -address 10.9.1.30 -netmask 255.0.0.0
C92A::> dns create -vserver vf1 -domains lab.priv -name-servers 10.0.1.10
C92A::> cifs server create -vserver vf1 -cifs-server VF1_TEMP -domain lab.priv


6) Create secondary SVM on C92B

We create a secondary SVM as destination for our temporary secondary vFiler.


C92B::> vserver create -vserver vf1-dr -rootvolume rootvol -aggregate data1 -rootvolume-security-style ntfs -language en.UTF-8


7) Configure 7MTT

The following commands will configure 7MTT for a secondary project (the secondary vFiler) and a primary project (the primary vFiler).


transition credentials add -h N7A -u root
transition credentials add -h 10.9.1.10 -u root
transition credentials add -h N7B -u root
transition credentials add -h C92A -u admin
transition credentials add -h C92B -u admin

transition cbt create -p 01_N7B_to_C92B -t secondary -n N7B -c 10.9.2.10 -f vf1_temp -h C92B -v vf1-dr
transition cbt volumepair add -p 01_N7B_to_C92B -v vf1_data -c vf1_data -g data1
transition cbt add-primary-seven-mode-system -p 01_N7B_to_C92B -h N7A -f 10.9.1.10 -d 10.9.1.10
transition cbt schedule add -p 01_N7B_to_C92B -n SCHED_01 -d 0-6 -b 0:0 -e 24:0 -t 25 -c 4 -x 100 -u 5:0
transition cbt show -p 01_N7B_to_C92B -r no
transition cbt precheck -p 01_N7B_to_C92B -r no

transition cbt create -p 02_N7A_to_C92A -t primary -n N7A -c 10.9.1.10 -f vf1 -h C92A -v vf1
transition cbt volumepair add -p 02_N7A_to_C92A -v vf1_data -c vf1_data -g data1
transition cbt lif add -p 02_N7A_to_C92A -i 10.9.1.20 -m 255.0.0.0 -g 10.0.0.1 -u e0c -n C92A-01
transition cbt add-secondary-cluster-mode-system -p 02_N7A_to_C92A -h C92B -v vf1-dr
transition cbt schedule add -p 02_N7A_to_C92A -n SCHED_01 -d 0-6 -b 0:0 -e 24:0 -t 25 -c 4 -x 100 -u 5:0
transition cbt show -p 02_N7A_to_C92A -r no
transition cbt precheck -p 02_N7A_to_C92A -r no

transition cbt start -p 01_N7B_to_C92B -n -r no
transition cbt start -p 02_N7A_to_C92A -n -r no


8) 7MTT Cutover

The following commands will cutover the 7MTT secondary and the 7MTT primary projects. 7MTT will establish DR snapmirrors from ONTAP primary to secondary.


transition cbt precutover -p 01_N7B_to_C92B -m no_test -r no
transition cbt precutover -p 02_N7A_to_C92A -m ro_test -r no

transition cbt cutover -p 01_N7B_to_C92B -o true -r no
transition cbt cutover -p 02_N7A_to_C92A -o true -r no

transition cbt delete -p 01_N7B_to_C92B
transition cbt delete -p 02_N7A_to_C92A


9) CIFS Server rename

Since we used a temporary AD machine account for our primary SVMs CIFS server, we can rejoin the CIFS server with the correct AD machine account.


C92A::> vserver cifs modify -vserver vf1 -status-admin down
C92A::> vserver cifs modify -vserver vf1 -cifs-server VF1

In order to create an Active Directory machine account for the CIFS server, you must supply the name and password of a Windows account with sufficient privileges to add computers to the "CN=Computers" container within the "LAB.PRIV" domain.

Enter the user name: administrator
Enter the password:

Warning: An account by this name already exists in Active Directory at CN=VF1,CN=Computers,DC=lab,DC=priv...
Ok to reuse this account? {y|n}: y

C92A::> vserver cifs show
          Server   Status   Domain/     Authentication
Vserver   Name     Admin    Workgroup   Style
--------- -------- -------- ----------- --------------
vf1       VF1      up       LAB         domain


10) SVM DR (SnapMirror for SVM) Configuration

The following commands configure an SVM DR relationship.


C92B::> snapmirror show
Source            Destination Mirror  Relationship
Path        Type  Path        State   Status         Healthy
----------- ---- ------------ ------- -------------- -------
vf1:vf1_data
            DP   vf1-dr:vf1_data
                              Snapmirrored
                                      Idle           true

C92B::> vserver stop -vserver vf1-dr
C92B::> snapmirror create -source-path vf1: -destination-path vf1-dr: -type DP -throttle unlimited -policy DPDefault -schedule hourly -identity-preserve true
C92B::> snapmirror resync -destination-path vf1-dr:

This Vserver has volumes which are the destination of volume-level SnapMirror relationships. A resync on the Vserver SnapMirror relationship will cause disruptions in data access. It will also convert the relationship-group-type of the volume SnapMirror relationships to "Vserver". Do you want to continue? y

C92B::> snapmirror show
Source            Destination Mirror  Relationship
Path        Type  Path        State   Status         Healthy
----------- ---- ------------ ------- -------------- -------
vf1:        DP   vf1-dr:      Snapmirrored
                                      Idle           true


11) Test CIFS access

The T drive will remain mapped. To check we can read the file we wrote earlier:


T:\>more message.txt
"TEST MESSAGE"


THE END

No comments:

Post a Comment