Migrating to NetApp ONTAP Using the 7-Mode Transition Tool … · Migrating to NetApp ONTAP Using...

Migrating to NetApp ONTAP Using the7-Mode Transition Tool Copy-BasedTransition

September 2016 | SL10284 Version 3.0

Migrating to NetApp ONTAP Using the 7-Mode Transition Tool Copy-Based Transition2 © 2016 NetApp, Inc. All rights reserved. NetApp Proprietary

TABLE OF CONTENTS

1 Migrating to NetApp ONTAP Using 7-Mode Transition Tool Copy-Based Transition................ 4

1.1........................................................................................................................................................4

1.2 Lab Introduction........................................................................................................................ 4

1.3 Prerequisites.............................................................................................................................. 5

1.4 Lab Environment....................................................................................................................... 5

1.4.1 Network Diagram.................................................................................................................................................. 5

1.4.2 Table of IDs and Systems.................................................................................................................................... 6

1.5 Lab Activities............................................................................................................................. 7

1.5.1 Getting Started with the 7MTT Tool..................................................................................................................... 7

1.6 Lab 1: Collect & Assess...........................................................................................................8

1.7 Lab 2: Migration.......................................................................................................................13

1.7.1 Task 1: Migrate NAS Volumes........................................................................................................................... 14

1.7.1.1 Pre-Migration................................................................................................................................................ 14

1.7.1.2 Create a Transition Project.......................................................................................................................... 15

1.7.1.3 Perform Migration.........................................................................................................................................38

1.7.1.4 Post-transition Activities............................................................................................................................... 56

1.7.2 Task 2: Migrate SAN Volumes........................................................................................................................... 57

1.7.2.1 Pre-Migration................................................................................................................................................ 57

1.7.2.2 Create a Transition Project.......................................................................................................................... 74

1.7.2.3 Perform Migration.........................................................................................................................................98

1.7.2.4 Post-transition Activities............................................................................................................................. 108

1.7.3 Task 3: Migrate SnapMirror Relationship......................................................................................................... 112

1.7.3.1 Pre-Migration.............................................................................................................................................. 112

1.7.3.2 Create a Transition Project........................................................................................................................ 115

1.7.3.3 Project Configuration – Secondary (Performed first)................................................................................. 120

1.7.3.4 Project Configuration – Primary.................................................................................................................132

1.7.3.5 Perform Migration – Secondary................................................................................................................. 146


1.7.3.6 Perform Migration - Primary.......................................................................................................................155

1.7.3.7 Post-transition Activities............................................................................................................................. 162

1.8 Logging in 7MTT and Collecting 7MTT Logs..................................................................... 163

1.9 Summary.................................................................................................................................165

1.10 References............................................................................................................................165

1.11 Version History.................................................................................................................... 166


1 Migrating to NetApp ONTAP Using 7-Mode Transition Tool Copy-BasedTransition

1.1

Contents

Lab Introduction 3

Prerequisites 3

Lab Environment 3

Network Diagram 3

Table of IDs and systems 4

Lab Activities 5

Getting Started with the 7MTT Tool 5

Lab 1: Collect & Assess 6

Lab 2: Migration 12

Task 1: Migrate NAS Volumes 13

Task 2: Migrate SAN Volumes 42

Task 3: Migrate SnapMirror Relationship 72

Logging in 7MTT and Collecting 7MTT Logs 103

Summary 104

References 105

Version History 105

1.2 Lab Introduction

The 7-Mode Transition Tool enables you to analyze your 7-Mode controllers, hosts, switches, and applicationsto assess their readiness for transition to clustered ONTAP. After assessment is complete you can then usethe 7_mode Transition Tool to plan your transition, and implement it using either a copy-based or a copy-freetransition methodology.

A copy-based transition uses SnapMirror technology to copy 7-Mode volumes and configurations from DataONTAP 7G and 7-Mode to ONTAP. In a copy-based transition you migrate data off of a 7-Mode controller ingroups of one or more volumes at a time, meaning you can keep your 7-Mode controller in operation servingsome volumes while other volumes are in the process of migration, and yet others have completed migration. Fora copy-based transition to be possible, the 7-Mode source controllers and disks must operate in parallel with thecluster-mode destination controllers, and both source and destination cluster must have enough disks available tosupport their own copies of the migrated data. The overall duration of the transition is longer as you must copy thedata from the source to the destination through SnapMirror, but the actual disruption of services is relatively shortbecause no hardware reconfiguration is necessary during cutover.

A copy-free transition uses disk shelf movement to migrate data from the 7-Mode source controllers to the cluster-mode destination controllers. In a copy-free transition, you disconnect all the disk shelves from the 7-Mode HApair and connect them to an HA pair in the destination cluster. A copy-free transition enables the re-use of the7-Mode disk shelves on the cluster-mode destination, thereby reducing hardware costs, but you also have tomigrate all the volumes on the source cluster at one time as part of the disk shelf moves. The overall duration ofa copy-free transition is generally shorter than a corresponding copy-based transition as there is no need to copy


data over the network from the source to the destination controllers, but the actual cutover is more disruptive andlonger-lasting that a copy-based transition due to all teh required hardware reconfiguration involved in disk shelfmoves and recabling.

1.2 Lab ObjectivesIn this lab you will use the 7-Mode Transition Tool to analyze a 7-Mode environment running CIFS, NFS, andiSCSI for transition to clustered ONTAP, and then migrate that environment to clustered ONTAP by performinga Copy-Based Transition. You will also learn what is involved in migrating Windows and Linux clients to use thetransitioned storage services from their new clustered ONTAP destination.

1.3 Prerequisites

To complete this lab successfully you should have the following prerequisite knowledge:

• Basic understanding of NetApp Data ONTAP (7-Mode).• Basic understanding of NetApp Clustered Data ONTAP.

1.4 Lab Environment

The following sections provide details about the lab environment.

1.4.1 Network DiagramThe following illustration depicts the lab environment:


Figure :

1.4.2 Table of IDs and SystemsThe following table provides the host information used for this lab:

Hostname Operating System Role/Function IP address User ID Password

FAS01 Data ONTAP 8.2.3 7-Mode Node 1 192.168.0.121 root Netapp1!

FAS02 Data ONTAP 8.2.3 7-Mode Node 2 192.168.0.122 root Netapp1!

CLUSTER1clustered Data ONTAP8.3.1

clustered Data ONTAP 192.168.0.101 AdminNetapp1!

JUMPHOSTMicrosoft WindowsServer 2012 R2 (64-bit)

Jump Host/ CIFS client 192.168.0.5DEMO\

AdministratorNetapp1!

RHEL1Red Hat EnterpriseLinux 6.4 (64-bit)

NFS client 192.168.0.12 rootNetapp1!


1.5 Lab Activities

The lab is broken out into various sections. You can choose to do all of the sections or you can choose individualsections.

This lab explores the fundamental features of the 7-Mode Transition Tool that you can use to perform thetransition from NetApp Data ONTAP (7-Mode) to NetApp Clustered Data ONTAP. You can choose to do the lab inits entirety or you can select individual sections you prefer.

1.5.1 Getting Started with the 7MTT Tool1. Double-click the 7MTT tool on the Desktop to get started.

1

Figure :

2. Fill in the credentials fields with username DEMO\Administrator, and password Netapp1!.3. Click Sign In.


2

3

Figure :

1.6 Lab 1: Collect & Assess

1. In the left side of the 7-Mode Transition Tool home screen, under the “Collect & Assess” section, clickCollect & Assess.

2. On the menu bar above the system list pane, click Add Systems.

1

2

Figure :


The “Add System” window opens.

3. Populate the fields as follows to add the 7-Mode system fas01 to the system list.

• “Name/IP:” 192.168.0.121• “Username:” root• “Password:” Netapp1!• “Type:” Data ONTAP Storage

4. Click Add Systems.

4

3

Figure :

The “Add System” window closes, and focus returns to the 7-Mode Transition Tool browser window.5. Using the following data, repeat the procedure in steps 2 through 4 to add the 7-Mode system fas02 to

the system list.

• “Name/IP:” 192.168.0.122• “Username:” root• “Password:” Netapp1!• “Type:” Data ONTAP Storage

6. Using the following data, repeat the procedure in steps 2 through 4 again to add the Linux system rhel1to the system list.

• “Name/IP:” 192.168.0.12• “Username:” root• “Password:” Netapp1!• “Type:” Red Hat Enterprise Linux

7. Using the following data, repeat the procedure in steps 2 through 4 one last time to add the Windowshost jumphost (the host on which the 7MTT tool is installed) to the system list.

• “Name/IP:” localhost• “Username”: <enter a single space>


• “Password:” <leave this field blank>• “Type:” Microsoft Windows

8. You should now see the four systems you just entered listed in the “Collect & Assess” pane.9. Select the checkboxes for all of the systems in the list.10. Click Create Transition Assessment Report.

8

910

Figure :

The “Create Transition Assessment Report” window opens.

11. Select a Data ONTAP target version of 8.3.1.12. Click Generate Report.

11

12

Figure :

Note: This lab utilizes ONTAP 8.3.1 as the target, but the migration tool also supports ONTAP 9targets.


The “Create Transition Assessment Report” window closes, and focus returns to the “Collect & Assess”view in the 7MTT browser window.

13. Scroll to the bottom of the window (if necessary) to monitor progress and wait for assessment tocomplete.

Attention: The tool reports that the assessment make take as long as 15 minutes to run, but inthis lab it should only take a couple of minutes.

14. Once the assessment completes, click the xls link that appears in the “Progress Monitor” pane todownload/view the Transition Assessment Workbook.

1314

Figure :

The “Opening AssessmentWorkbook.xml” window opens.15. Click OK to open the document.


15

Figure :

The “Opening AssessmentWorkbook.xml” window closes, and Microsoft Excel opens and displays theworkbook's “Data Collection Summary” tab. This page provide links to the various sub-reports availablein this workbook.

16. Click the Transition Feasibility (CBT) link on the Content tab (or alternately find and select theTransition Feasibility (CBT) tab at bottom of the spreadsheet window).

17. See if there are any blocking errors that would prevent a Copy-Based Transition. In this lab you will notsee any blocking errors listed on that page.

A few of the many other tabs you can review for additional messages include:

• “Transition PreCheck Summary” Tab. Check to see if any objects in use on your 7-Modesystems that have changed in clustered Data ONTAP are applicable to your environment. Ifso, refer to the associated corrective action.

• “SAN Hosts” Tab: Check for MPIO Assessment to see if driver is supported.• “SAN Host HBAs” Tab: check for HBA assessment to see if driver is supported.

18. Close Excel.


16

18

17

Figure :

The workbook closes, and focus returns to the “Collect & Assess” page in the 7-Mode Transition Toolbrowser window.

19. Close the Collect and Assess tab.

19

Figure :

The browser displays the 7-Mode Transition Tool Home tab.

1.7 Lab 2: Migration

This section of the lab consists of three tasks. They are…


1. Task 1: Migrate NAS Volumes2. Task 2: Migrate SAN Volumes3. Task 3: Migrate SnapMirror Relationship

Each is independent of the others, so you can select one or more of these tasks to perform in the same lab. Allof the tasks follow the same high-level process shown in the Migration Process Overview diagram, but thereare implementation differences in each due to their use of different storage technologies, and also to showcasedifferent options you have with regards to handling networking, schedules, and so on during transition. As aresult, there is value to be gained by going through all three tasks if you have the time to do so, otherwise pick theone or two that are of most interest to you.

Figure : Migration Process Overview

1.7.1 Task 1: Migrate NAS VolumesThis is the same procedure as SAN volumes except you have the ability to do testing before you cutover toclustered Data ONTAP. Pre-cutover testing is not available if one of the volumes in the project contains a LUN.

1.7.1.1 Pre-Migration

In this section you will verify the existence of a sample data file on a volume that you will transition later in the lab.

1. From the task bar of Jumphost, launch Windows Explorer.

1

Figure :

2. Browse to the \\192.168.0.151\cifstest share, and then the cifsdata folder.3. Verify the presence of the file datafile1.txt.


The specific contents of this file are not significant, it's only intended to demonstrate that the file getspreserved during the transition. You may open the file now if you wish; it simply contains a repeatedsequence of the string “foo”. If you do open it then please close it when you are finished examining it.

4. Close Windows Explorer.

2 4

3

Figure :

1.7.1.2 Create a Transition Project

1. On the 7-Mode Transition Tool Home tab in the browser, under the “Plan and Design” section, selectCopy-Based Transition.

2. Click Start Planning.


1

2

Figure :

A new tab entitled “(CBT) Untitled Project” opens in the 7MTT tool.

3. Add “cluster1” to the list of Clustered Data ONTAP systems that you will be transitioning to by populatingthe fields in the “Enter Device Credentials” box as follows:

• “Hostname:” 192.168.0.101• “Username:” admin• “Password:” Netapp1!

4. Click Add.


3

4

Figure :

5. An entry for “cluster1” now appears in the list of “Clustered Data ONTAP Systems”.6. The “fas01” and “fas02” controllers you added to the tool during the “Collect & Assess” exercise should

already appear in the list of 7-Mode controllers. If you skipped that exercise, add them now by repeatingsteps 3 & 4 using the following information:

• “fas01 Hostname:” 192.168.0.121• “fas02 Hostname:” 192.168.0.122• “Username:” root• “Passoword:” Netapp1!

7. Click the Next button on the far right side of the window that sits just above the list of Clustered DataONTAP systems. This launches the wizard for the Plan & Design process.


5

6

7

Figure :

The Plan & Design wizard advances to the “Select Source Volumes” stage.

8. In the “Select 7-Mode Controller” pane on the left, select fas01.9. In the “Volume Information” pane on the right, in the row for the volume vol1_NAS, check the Transition

as stand-alone checkbox.10. The “vol1_NAS” volume is now listed in the “Volume(s) Selected for Transition Project” pane at the

bottom of the window.11. Click the Create Project and Continue button on the right side of the page.


89

10

11

Figure :

The “Project Details” window opens.

12. Set the “Project Name” field to NAS.13. Click Save.


12

13

Figure :

The “Project Details” windows closes, and the Plan & Design wizard advances to the “Select Data CopyIP” stage. This is where you select which IP addresses on the 7-mode system should be used as thesource for the copy operation.

14. Observe that the title of the current tab in the 7MTT tool has changed to “(CBT) NAS”.15. The “Data Copy IP” field has been pre-populated with 192.168.0.121, the management IP address of

fas01. Update this field to specify an address of 192.168.0.153, which is the address of a differentnetwork interface on fas01 that is intended for data access.

16. Set the “Multipath IP” field to 192.168.0.152 so the data transfer will be load balanced across boththese interfaces.

17. Click the Next button on the far right middle of the page.


14

15

16

17

Figure :

The Plan & Design wizard advances to the “Select SVM” stage. This is where you will select whichSVM on the destination cluster will be the target of the copy operation.

18. In the “Select an SVM” pane on the right, select the checkbox for vserver1.19. Click the Next button in the middle on the right side of the page.


18

19

Figure :

The Plan & Design wizard advances to the “Map Volumes” stage. This is where you specify the targetaggregate and volume names for the copy operation.

20. The “Select Target Volume mount policy” drop-down in the middle of the page controls which targetvolume mount path scheme will apply to the volumes in this transition. Hover the mouse over the bluequestion mark icon just to the right of this field to see the available schemes. The default “Preserve 7-Mode Mount paths” value is sufficient for this lab exercise.

21. You can modify which target aggregate and which target volume name to use for the volume(s)involved in this transition. Accept the default values.

22. Click the Next button in the middle of the far right side of the window.


20

21

22

Figure :

The Plan & Design wizard advances to the “Network Configuration” stage. This is where you selectwhich IP addresses on the destination cluster will be used for the transition.

There are two ways to specify new LIFs you want to configure on the target vserver. You can eitherchoose to transition existing IPs from the 7-Mode controller, or you can specify details of new LIFs youwant to configure. For this exercise you will migrate an existing LIF.

23. In the left side of the window, click the Select 7-Mode LIFbutton.


23

Figure :

The “Select 7-Mode LIF” window opens.

24. Select the checkbox for the LIF with the IP address of 192.168.0.151.25. You can choose which cluster node and network port this IP address will be assigned to. Accept the

default values.26. Click Save.

25

26

24

Figure :


The “Select 7-Mode LIF” window closes, and focus returns to the “Network Configuration” stage of thePlan & Design wizard.

27. An entry for the “192.168.0.151” address now appears in the lower pane of the window.28. Click the Next button located in the middle of the far right side of the window.

27

28

Figure :

The Plan & Design wizard advances to the “Configure Schedule” stage. This is where you selectwhich time windows are permissible for the SnapMirror operations that will be involved in this transitionproject.

While it is possible to create very detailed and fine-grained schedules with this tool, this exercise willshow the use of relatively simple schedules. You will create two schedules here, the first of whichcovers “daytime” hours, and limits the amount of bandwidth that the SnapMirror operations canconsume to just 100MB/sec. The second schedule covers “nighttime” hours, and allows the SnapMirroroperations to consume as much bandwidth as is available. These combined schedules permit round-the-clock transitions.

29. In the left side of the window, click the Create Schedule button.


29

Figure :

The “Create Data Copy Schedule for Baseline and Incremental Updates” window opens.

30. Name the first schedule PeakHours.31. In the “Recurring Days” box, select the Daily radio button.32. In the Time Interval section, set the fields as follows:

• “Start Time:” 07 Hrs, 00 Mins• “Duration:” 12 Hrs, 00 Mins• “Update Frequency:” 00 Hrs, 30 Mins

33. In the “Parameters for Transition Data Copy Operations” section, set the fields as follows:

• “Maximum Number of Concurrent VSM Transfers:” 3• “Throttle Limit:” Not Exceeding, value = 100

34. Click Create.


30

31

32

33

34 33

Figure :

The “Create Data Copy Schedule for Baseline and Incremental Updates” window closes, and an“Informational” window now opens notifying you that the schedule has been added.

35. Click OK.


35

Figure :

The “Informational” window closes, and focus returns to the “Configure Schedule” stage of the Plan &Design wizard.

36. The schedule you just created now appears in the list of schedules.37. Click Create Schedule again.

36

37

Figure :


38. Name the second schedule NonPeakHours.39. In the “Recurring Days” box, select the Daily radio button.40. In the Time Interval section, set the fields as follows:

• “Start Time:” 19 Hrs, 00 Mins• “Duration:” 12 Hrs, 00 Mins• “Update Frequency:” 00 Hrs, 30 Mins


• “Maximum Number of Concurrent VSM Transfers:” 3


• “Throttle Limit:” Maximum42. Click Create.

38

39

40

41

42

41

Figure :

The “Create Data Copy Schedule for Baseline and Incremental Updates” window closes. An“Informational” window now opens notifying you that the schedule has been added.

43. Click OK.


43

Figure :


44. You now see two schedules in the list of schedules.45. In the middle of the far right side of the window, click Next.

44

45

Figure :

The Plan & Design wizard advances to the “Plan Configuration” stage. This is where you can furthercustomize the transition configuration, including but not limited to modifying NFS export rules, snapshotschedules, CIFS and NFS options, and so on.

46. For this exercise you will be accepting all the default selections here, so click Save and go toDashboard on the right side of the window.


46

Figure :

The Plan & Design wizard terminates, and the 7-Mode Transition Tool switches over to the MigrationDashboard. This is where the 7-Mode Transition Tool actually invoke migrations, but in this exerciseyou are going to focus on just the precheck portion. A precheck runs an analysis of the source andtargets controllers involved in the current transition project, looking for configuration problems that mightblock the transition.

47. Click Run Precheck.


47

Figure :

A precheck operation status window opens, and tracks the progress of the various checks that thetool is running. Individual checks can return, in increasing order of severity, informational, warning, orerror status results, and in most cases the tool provides suggestions for remediating the issue. Errorstatus results will block a transition completely. Warnings and informational message will not block atransition, but the issues they point out may produce undesireable transition results and so you shouldreview them and consider whether you want to take corresponding action.

It is quite common for the tool to find issues at this stage that require remediation. The specific issuesthe tool will find can vary significantly from system to system, and in the interests of time this lab cannotcover all of the possibilities. However, this exercise is designed to generate an error to give you a flavorfor what the experience is like.

48. The prechecks complete, but return an overall operation status of “Failed”.49. The check type summary list indicates that an error occured during the CIFS prechecks.50. Expand the CIFS prechecks section.


48

49

50

Figure :

51. If necessary, scroll down to view the details of the specific CIFS check that failed.52. The “Message” column details the specific problem the tool found. In this example you are using a pre-

existing SVM (vserver1) as the target for the transition, and the transition will not be able to copy thesource controller's CIFS local users and groups to the destination SVM because that SVM already hasCIFS local users and groups that may conflict.

53. The “Recommended Action” column presents a list of some potential remediation actions you mighttake in response. In this exercise you will take the first listed course for action since the shares you willbe transitioning do not use CIFS local users or groups.

54. You can click the SVM's link in the “Affected Objects” column to see, in this case, that cluster1 isaffected by this error.

55. Click Close.


5152

53

54

55

Figure :

The precheck operation status windows closes, and focus returns to the Migration Dashboard.

56. Notice that the circle for Preparation phase of the transition workflow is red, indicating an error.57. The button under the Baseline Data Copy phase is also greyed out, since the tool will not allow a

baseline copy operation to start if the precheck has failed.58. Navigate to Edit Project > Plan Configuration.


56

57

58

Figure :

The tool returns to the “Plan Configuration” stage of the Plan and Design wizard.

59. In the “SVM Configuration” pane, under the CIFS section, uncheck the CIFS Local Users and Groupscheckbox. You are doing this because the remediation action you chose excludes the transition of localusers and groups.

60. On the far right side of the window, click Save and Go to Dashboard.


59

60

Figure :

The 7-Mode Transition Tool switches over to the “Migration Dashboard” again.


61

Figure :

The precheck operation status window opens again.

62. This time the precheck completes with an operation status of “Successful (With warnings)”.


63. Feel free to examine some of the warning messages the precheck generated, but this exercise doesnot require you to act on any of these warnings.

64. Click Close.

62

63

64

Figure :

The precheck operation status windows closes, and focus returns to the “Migration Dashboard”.

65. The Preparation phase of the transition workflow now shows a green circle.


65

Figure :

1.7.1.3 Perform Migration

You should still be on the Migration Dashboard from the end of the preceding exercise. In this exercise you willinitiate the actual migration.

1. Click Start Baseline.

1

Figure :

A “Warning” window opens that recommends you address all the precheck results before proceeding.2. Click Yes.


2

Figure :

The “Warning” window closes, and the “Start Baseline, Operation Status” window opens and runs theprechecks again.

Note: While it may seem redundant to run the prechecks again, in production environments asignificant amount of time may have passed between the creation of the project and the start ofthe migration. Rerunning the prechecks evaluates any changes that may have been made to thesource or destination in the interim.

3. Once the prechecks complete, click Close.

3

Figure :


The “Start Baseline, Operation Status” window closes, and focus returns to the Migration Dashboard.

The lower pane of the Migration Dashboard now opens to the Volumes tab, and displays the progress ofthe baseline transfer. The baseline transfer will be subject to the schedule and bandwidth restrictions youset up for your transition project. Depending on how restrictive those restrictions are, this could mean thebaseline transfer may not actually start until a later time. Additionally, depending on how large your datafootprint is, it may takes hours or days for the baseline transfer to complete. In this lab exercise the datafootprint is very small (just 1 file), and the schedule is largely unrestricted, so the baseline transfer shouldcomplete in just a few moments.

4. Periodically click Refresh until the Baseline Data Copy circle turns green.5. Check the Test Mode checkbox.6. Click Apply Configuration.

4

5

6

Figure :

The “Apply Configuration (Precutover)” window opens.

7. Check the “Apply configuration in test mode” checkbox. This indicates that you want to temporarily andpartially configure the destination SVM with the resulting transition configuration. This allows you to tryout portions of the resulting configuration in advance of the permanent transition.

8. Click Continue.


7

8

Figure :

The “Apply Configuration (Precutover)” window closes, and the “Apply Configuration (Precutover)Operation Status“ window opens.

9. The “Operation Status” will show “Running...” until the operation completes, at which point it changes to“Successful (With warnings).

10. Click Close.


9

10

Figure :

The “Apply Configuration (Precutover) Operation Status“ window closes, and focus returns to theMigration Dashboard.

11. Note that the Precutover circle is yellow, indicating the project is running in test mode.

11

Figure :

Look at cluster1 to see the storage services from fas01 that are now temporarily available on cluster1as part of the test phase.

12. Go to the desktop of the Jumphost, and launch NetApp OnCommand System Manager.


12

Figure :

OnCommand System Manager opens and eventually displays a list of storage systems.

13. Double-click the entry for cluster1.

13

Figure :

14. Enter the username admin, and the password Netapp1!.15. Click Sign In.


14

15

Figure :

16. In the left pane of System Manager, navigate to Storage Virtual Machine > cluster1 > vserver1 >Storage > Volumes.

17. In the “Volumes” pane, observe that the “vol1_NAS” volume reports a status of “Online”.


16

17

Figure :

18. In the left pane, click Shares.19. The “Shares” pane shows a share named “ciftstest”.


18

19

Figure :

20. In the left pane, navigate to the Cluster > cluster1 > Configuration > Network.21. In the “Network” pane select the Network Interfaces tab.22. Locate the interface with the IP address 192.168.0.151, and note that this LIF is disabled. This is

expected, because this IP is currently in use on the 7-Mode system. It will automatically turn online aftertransition.

23. Click Create.


20

21

22

23

Figure :

The “Create Network Interface” window opens.

Now create a temporary LIF that has a spare IP address that you can use to test data access to thetransitioned volume.

24. Populate the fields in this window as follows:

• “Name:” TestLIF• “Interface Role:” Serves Data• “SVM:” vserver1• “Protocol Access:”

• CIFS: checked• NFS: checked

• “Subnet:” Default IP Space• Use a specific IP address: 192.168.0.132• “Port:” cluster1-01 e0c

25. Click Create.


25

Figure :

The “Create Network Interface” window closes, and focus returns to the Network pane in SystemManager.

26. The new LIF, “TestLIF”, now appears in this pane's list of network interfaces.


26

Figure :

27. From the desktop on the Jumphost, open Windows Explorer and navigate to the path \\192.168.0.132\cifstest\cifsdata. Enter this share path directly in the Windows Explorer addressbar.

28. Right-click in the white space of the folder and select New > Text Document from the context menu.Accept the default file name.


28

Figure :

Note: Observe that the file creates successfully, meaning you you have full read-write capabilityto the share during test mode.

29. Return to the Migration Dashboard (click the 7-Mode Transition Tool tab in the browser) and click onFinish Testing.

29

Figure :


The “Finish Testing (Resync) Operation Status” window opens and begins resyncing the SVM's targetvolumes back to their pre-test state.

30. When the resync operation completes, click Close.

30

Figure :

The “Finish Testing (Resync) Operation Status” window closes, and focus returns to the MigrationDashboard.

31. The Precutover circle is now green.

31

Figure :

32. Return to the Windows Explorer window, and refresh the path by clicking the refresh icon.33. Notice the text file you created during precutover testing no longer exists on the share.34. Right-click inside the folder and attempt to create a file. This will fail since the share is now read-only

again because test mode is complete.35. Close Windows Explorer.


3233

34

35

Figure :

36. Return to the 7MTT Migration Dashboard.

Note: While the dashboard indicates that you are technically ready to perform a storagecutover. In practice you would first want to perform an incremental update so you can minimizethe amount of data you will have to transfer during the actual storage cutover step.

37. Click Update Now to initiate an incremental update.

37

Figure :

The “Transition Update” window opens, giving you an opportunity to modify the SnapMirror transferthrottling limits.

38. Click Continue.


38

Figure :

The “Transition Update” window closes, and the “Update Operation Status” window opens.

39. After the SnapMirror update operations complete, click Close.

39

Figure :

The “Update Operation Status” window closes, and focus returns to the Migration Dashboard.

Note: In a production environment you would now stop client activity to the volumes in themigration project so that there will be no client-initiated corruption to the volume, as the cutoveris a disruptive process. However, since this lab does not contain any active clients, you will skipthis step for this exercise.

40.Click Complete Transition.


40

Figure :

A “Warning” window opens, once again advising you that there are warnings in this transition projectthat you should address.

41. None of the specific warnings for this lab exercise transition are significant, so click Yes.

41

Figure :

The “Warnings” window closes, and the “Complete Transition” window opens.

42. Note the checkbox indicating that the source volumes should be taken offline after the transition.43. Click Continue.


42

43

Figure :

The “Complete Transition” window closes, and the “Complete Transition Operation Status” windowopens.

44. When the cutover operation completes, the Operation Status changes from “Running...” to “Successful(With warnings)”.

45. Click Close.

44

45

Figure :

The “Complete Transition Operation Status” window closes, and focus returns to the MigrationDashboard.

46. The circle for the “Storage Cutover” phase is now green.


46

Figure :

The migration is now complete.

1.7.1.4 Post-transition Activities

1. Verify data access to the transition share by launching Windows Explorer and navigating to \\192.168.0.151\cifstest\cifsdata.

Note: You are specifying here the permanant IP address you selected to transition as part of theproject, not the IP address of the temporary test LIF you created during the test phase.

2. Observe that “datafile1.txt” is present. If you open it you will see the expected sequence of repeating“foo” strings.

3. Verify you have write access to this share by trying to create a file. This should succeed.4. Close Windows Explorer.


1

2

3

4

Figure :

You can now use System Manager or the CLI to examine cluster1 to verify that the 192.168.0.151 IP addressis now configured for a LIF assigned to the vserver1 SVM. You can likewise look at fas01 to verify that192.168.0.151 is no longer configured as an address on that system, and that the vol1_NAS volume is offlinethere (although the volume still exists). However, in the interest of brevity, this is an optional exercise.

The test LIF you created on cluster1 is also still configured and active, although the only clients that would beaccessing data through that address are ones that you might have tested with during the test phase. Ordinarilyyou might now want to deconfigure that interface, but it's presence causes no problems in this lab, so thisexercise will not bother with that cleanup task.

1.7.2 Task 2: Migrate SAN VolumesThis is the same procedure as NAS volumes, except you do not have the ability to do testing before you cutoverto clustered Data ONTAP. The ability to test before storage cutover is not available if one of the volumes in theproject contains a LUN.

The LUN in this exercise is mounted on the Windows Jumphost.


1. If System Manager is not already running, on the desktop of the jumphost launch NetApp OnCommandSystem Manager.


1

Figure :

System Manager opens, and eventually displays a list of storage systems.

2. Select the System Manager entry for fas01.demo.netapp.com.3. Click Login.

2

3

Figure :

4. If prompted, log in with userid root and password Netapp1!5. In the left pane of System Manager, navigate to fas01 > Storage > LUNs.6. In the LUNs pane, select the entry for LUN_01.7. Select the Initiators tab on the bottom of the window.8. Examine the “Initiator Name” and “Group Name” (igroup) values. You will be transitioning these details

along with the LUN during this lab exercise.


5

6

78

Figure :

9. On the desktop of Jumphost, launch Computer Management.


9

Figure :

The “Computer Management” window opens.

10. Navigate to Storage > Data ONTAP DSM Management.11.

Verify that the LUN “/vol/vol2_SAN/LUN_01” on fas01 is connected as the Z: drive on Jumphost.12. Close the “Computer Management” MMC.

10

11

12

Figure :

The “Computer Management” MMC window closes.


13. On the taskbar of Jumphost, launch Windows Explorer.

13

Figure :

14. Navigate to the Z: drive.15. Verify the existence of the “LUN_Data.txt” file on the Z: drive.16. Close Windows Explorer.

14

15

16

Figure :

The Windows Explorer window closes.

Before you initiate the LUN transition you need to add to the the LUN client's iSCSI initiater the IPaddresses of the iSCSI target LIFs you will be transitioning to on cluster1. Those target LIFs alreadyexist on cluster1, so now is a good time to add these addresses to the client initiator.

17. On the desktop of Jumphost, launch iSCSI Initiator.


17

Figure :

The “iSCSI Initiator Properties” window opens.

18. Select the Discovery tab.19. Click Discover Portal....


18

19

Figure :

The “Discover Target Portal” window opens.

20. In the “IP address or DNS name:” field, enter the address 192.168.0.175. This is one of the IPaddresses you will configure for the iSCSI LIF on cluster1 in the following exercise.

21. Click Advanced....

20

21

Figure :

The “Advanced Settings” window opens.

22. Set the fields in this window as follows:

• “Local adapter”: Microsoft iSCSI Initiator• “Initiator IP”: 192.16.0.5

23. Click OK.


22

23

Figure :

The “Advanced Settings” window closes, and focus returns to the “Discover Target Portal” window.

24. Click OK.


24

Figure :

The “Discover Target Portal” window closes, and focus returns to the “iSCSI Initiator Properties”window.

25. Select the Targets tab.26. In the Discovered targets list, select the entry for the “Inactive” target.27. Click Properties.


25

26

27

Figure :

The “Properties” window opens.

28. Click Add session.


28

Figure :

The “Connect to Target” window opens.

29. Check the Enable multi-path checkbox.30. Click Advanced....

29

30

Figure :



• “Local Adapter”: Microsoft iSCSI Initiator• “Initiator IP”: 192.168.0.5• “Target Portal IP”: 192.168.0.175


32. Click OK.

31

32

Figure :

The “Advanced Settings” window closes, and focus returns to the “Connect To Target” window.

33. Click OK.


33

Figure :

The “Connect To Target” window closes, and focus returns to the “Properties” window.34. Click Add session again to add the second iSCSI LIF.

34

Figure :

The “Connect To Target” window opens again.

35. Check the Enable multi-path checkbox.36. Click Advanced....


35

36

Figure :



• “Local Adapter”: Microsoft iSCSI Initiator• “Initiator IP”: 192.168.0.5• “Target Portal IP”: 192.168.0.176

38. Click OK.


37

38

Figure :

The “Advanced Settings” window closes, and focus returns to the “Connect To Target” window.

39. Click OK.


39

Figure :

The “Connect To Target” window closes, and focus returns to the “Properties” window.40. Click OK.


40

Figure :

The “Properties” window closes, and focus returns to the “iSCSI Initiator Properties” window.

41. In the “Discovered targets” section, verify that both the 7-Mode and clustered Data ONTAP targets areconnected.

42. Click OK.


41

42

Figure :

The “iSCSI Initiator Properties” window closes.


1. If you don't already have the 7-Mode Transition Tool running from a previous exercise, launch it from thedesktop of Jumphost. (If you do have it open, select the 7-Mode Transition Tool tab in your browserand then skip to step 3.)


1

Figure :

2. Log in as user DEMO\Administrator, with the password Netapp1!.


2

Figure :

3. Click Plan & Design.

3

Figure :

The “Plan Migration” window opens.

4. Select the Copy-Based Transition radio button.5. Click Start Planning.


4

5

Figure :

The “Plan Migration” window closes, and focus returns to the 7MTT browsers window, where a new“(CBT) Untitled Project” tab has opened.

6. If there are not already entries in the 7-Mode Controllers list for fas01 and fas02, or there is not alreadyan entry in the Clustered Data ONTAP Systems list for cluster1, then use the controls in the “EnterDevice Credentials” box to add these systems to their repective lists by using the following values::

• cluster1 Hostname: 192.168.0.101, Username: admin, Password: Netapp1!• fas01 Hostname: 192.168.0.121, Username: root, Password: Netapp1!• fas02 Hostname: 192.168.0.122, Username: root, Password: Netapp1!

7. After populating the device credentials fields for each of the systems listed in the preceding step, clickAdd .

8. All 3 controllers now appear in their respective lists.9. On the far right side of the window, click Next. This launches the wizard for the Plan & Design process.


6

7

8

9

Figure :


10. In the “Select 7-Mode Controller” list select the entry for fas01.11. In the “Volume Information” list locate the entry for “vol2_SAN”, and in that row check the Transition

stand-alone checkbox.12. The window updates, and an entry for this volume now appears in the “Volume(s) Selected for

Transition Project” list at the bottom of the window.13. In the middle of the far right of the window, click Create Project and Continue.


10 11

12

13

Figure :

A “Warning” window opens indicating that this sub-project contains SAN volumes, and that precutoverread/write mode will be disabled. Read the window text for further details.

14. Click OK.


14

Figure :

The “Warning” window closes, and the “Project Details” window opens.15. Set the “Project Name” field to LUN.16. Click Save.

15

16

Figure :

The “Project Details” window closes, and the Plan & Design wizard now advances to the “Select DataCopy IP” stage. This is where you select which IP addresses on the 7-mode system should be used asthe source for the copy operation.

17. Note that the text in the former “(CBT) Untitled Project” tab has now been updated to reflect the projectname you just entered. It now displays “(CBT) LUN”.

18. In the “Enter the Data Copy and Multipath IPs” section of the window, populate the fields as follows:


• “Data Copy IP”: 192.168.0.153• “Multipath IP”: 192.168.0.152

19. In the middle of the far right side of the page, click Next.

17

18

19

Figure :

The Plan & Design wizard advances to the “Select SVMs” stage. This is where you will select whichSVM on the destination cluster will be the target of the copy operation.

20. In the “Select an SVM” list, check the checkbox for vserver1.21. In the middle of the far right of the window, click Next.


20

21

Figure :



23. You can modify which target aggregate and which target volume name to use for the volume(s)involved in this transition. Accept the default values.

24. Click Next button in the middle of the far right side of the window.


22

23

24

Figure :

The Plan & Design wizard advances to the “Network Configuration” stage. This is where you selectwhich IP addresses on the destination cluster will be used for the transition.

Since this transition project leverages pre-existing iSCSI LIFs on the destination cluster, there is nothingyou need to do in the stage.

25. Click the Next button located in the middle of the far right side of the window.


25

Figure :

The Plan & Design wizard advances to the “Configure Schedule” stage. This is where you select whichtime windows are permissible for the SnapMirror operations that are involved in this transition project.

While it is possible to create very detailed and fine-grained schedules with this tool, this exerciseillustrates the use of relatively simple schedules. You create two schedules here; the first covers“daytime” hours, and limits the amount of bandwidth that the SnapMirror operations can consume tojust 100MB/sec. The second schedule covers “nighttime” hours, and allows the SnapMirror operationsto consume as much bandwidth as is available. These combined schedules permit round-the-clocktransitions.



26

Figure :


27. Name the first schedule PeakHours.28. In the “Recurring Days” box, select the Daily radio button.29. In the Time Interval section, set the fields as follows:

• “Start Time”: 07 Hrs, 00 Mins• “Duration”: 12 Hrs, 00 Mins• “Update Frequency”: 00 Hrs, 30 Mins


• “Maximum Number of Concurrent VSM Transfers”: 3• “Throttle Limit”: Not Exceeding, value = 100

31. Click Create.


27

28

29

30

3130

Figure :


32. Click OK.


32

Figure :


33. The schedule you just created now appears in the list of schedules.34. Click Create Schedule again.

33

34

Figure :


35. Name the second schedule NonPeakHours.36. In the “Recurring Days” box, select the Daily radio button.37. In the Time Interval section, set the fields as follows:

• “Start Time”: 19 Hrs, 00 Mins• “Duration”: 12 Hrs, 00 Mins• “Update Frequency”: 00 Hrs, 30 Mins


• “Maximum Number of Concurrent VSM Transfers”: 3• “Throttle Limit”: Maximum


39. Click Create.

35

36

37

38

38

39

Figure :


40. Click OK.


40

Figure :


41. You now see two schedules in the list of schedules.42. In the middle of the far right side of the window, click Next.

41

42

Figure :


43. In the “SVM Configuration” pane, uncheck the Select All checkbox.44. In the “Volume Configuration” pane, uncheck the Select All checkbox.45. Still in the “Volume Configuration” pane, check the SAN checkbox.46. Click Save and go to Dashboard on the right side of the window.


43 44

45

46

Figure :

The Plan & Design wizard terminates, and the 7-Mode Transition Tool switches over to the MigrationDashboard. This is where the 7-Mode Transition Tool actually invokes migrations, but in this exerciseyou are going to focus on just the precheck portion. A precheck runs an analysis of the source andtargets controllers involved in the current transition project, looking for configuration problems that mightblock the transition.



47

Figure :

A precheck operation status window opens, and tracks the progress of the various checks that thetool is running. Individual checks can return, in increasing order of severity, informational, warning, orerror status results, and in most cases the tool provides suggestions for remediating the issue. Errorstatus results will block a transition completely. Warnings and informational message will not block atransition, but the issues they point out may produce undesireable transition results and so you shouldreview them and consider whether you want to take corresponding action.

It is quite common for the tool to find issues at this stage that require remediation. The specific issuesthe tool will find can vary significantly from system to system, and in the interests of time this lab doesnot cover all of the possibilities. However, this exercise is designed to generate an error to give you aflavor for what the experience is like.

48. The prechecks complete, but return an overall operation status of “Failed”.49. The check type summary list indicates that an error occured during the WAFL prechecks.50. Expand the WAFL prechecks section.


48

49

50

Figure :

51. If necessary, scroll down to view the details of the specific WAFL check that failed.52. The “Message” column details the specific problem the tool found. In this example inode to pathname

translation is disabled on the 7-mode vol2_SAN volume, and such translation cannot be disabled inClustered ONTAP.

53. The “Recommended Action” column presents a list of some potential remediation actions you mighttake in response. In this exercise you will implement this recommended action to correct the problem,so please read the full recommendation.

54. The 7-Mode Volumes link will display a list of the affected volumes.


51

52 53

54

Figure :

55. On the taskbar of Jumphost, launch PuTTY.

55

Figure :

The “PuTTY Configuration” window opens.

56. Double-click the saved session profile for fas01.


56

Figure :

A PuTTY session window opens to fas01.

57. Log in as user root, with the password Netapp1!.58. Enable inode to pathname translation for the vol2_SAN volume by setting the volume's no_i2p option

to off.

fas01> vol options vol2_SAN no_i2p offfas01>

59. Exit the PuTTY session to fas01.

fas01> exit

The PuTTY window closes.60. Bring the 7-Mode Transition Tool browser window back into focus. The browser should still be

displaying the “Precheck Operation Status” window.61. Click Close.


61

Figure :

The “Precheck Operation Status” window closes, and focus returns to the Migration Dashboard.

62. Notice that the circle for Preparation phase of the transition workflow is red, indicating an error.63. The button under the Baseline Data Copy phase is also greyed out, since the tool will not allow a

baseline copy operation to start if the precheck has failed.64. Click Run Precheck.


62

6364

Figure :

The precheck operation status window opens again.

65. This time the precheck completes with an operation status of “Successful (With warnings)”.66. Feel free to examine some of the warning messages the precheck generated if you'd like to, but this

exercise does not require you to act on any of these warnings.67. Click Close.


65

66

67

Figure :


68. The Preparation phase of the transition workflow now shows a green circle.

68

Figure :


1.7.2.3 Perform Migration

You should still be on the Migration Dashboard from the end of the preceding exercise. In this exercise you willinitiate the actual migration.

1. Click Start Baseline.

1

Figure :

A “Warning” window opens that recommends you address all the precheck warning before proceeding.2. Click Yes.

2

Figure :

The “Warning” window closes, and the “Start Baseline Operation Status” window opens and runs theprechecks again.




3

Figure :

The “Start Baseline Operation Status” window closes, and focus returns to the Migration Dashboard.

The lower pane of the Migration Dashboard now opens to the “Volumes” tab, and displays the progressof the baseline transfer. The baseline transfer is subject to the schedule and bandwidth restrictions youset up for your transition project. Depending on how restrictive those restrictions are, this could mean thebaseline transfer may not actually start until a later time. Additionally, depending on how large your datafootprint is, it may takes hours or days for the baseline transfer to complete. In this lab exercise the datafootprint is very small (just 1 file), and the schedule is largely unrestricted, so the baseline transfer shouldcomplete in moments.

4. Periodically click Refresh until the Baseline Data Copy circle turns green.5. The “Test Mode” checkbox here is greyed out. Click the ? icon to its' right to recall why.6. Click Apply Configuration.


4

5

6

Figure :


7. Click Continue.

7

Figure :



9. Click Close.


8

9

Figure :

The “Apply Configuration (Precutover) Operation Status“ window closes, and focus returns to theMigration Dashboard, where the Precutover circle has turned green.

Note: While the Migration Dashboard indicates that you are technically ready to perform astorage cutover, in practice you will first want to perform an incremental update, so you canminimize the amount of data you will have to transfer during the actual storage cutover step.

10. The Precutover circle has turned green.11. Click Update Now to initiate an incremental update.


10

11

Figure :


12. Click Continue.

12

Figure :




13

Figure :


Note: Before you initiate the cutover, you should disable client access to the LUN to avoidpotential data loss or corruption that might otherwise occur, as the cutover is a disruptiveprocess.

14. On the desktop of Jumphost, launch Computer Management.

14

Figure :


The “Computer Management” MMC window opens.

15. Navigate to Computer Management (Local) > Storage > Disk Management.16. Right click on Disk1, and select Offline from the context menu.

15

16

Figure :

17. Disk 1 now shows as “Offline” in the MMC.

17

Figure :

18. Minimize the “Computer Management” MMC window as you will need it again later.19. Return to the “7-Mode Transition Tool” browser window.20. Click Complete Transition.


19

20

Figure :

A “Warning” window opens, again advising you that there are warnings in this transition project that youshould address.


21

Figure :




22

23

Figure :



25. Click Close.


24

25

Figure :




26

Figure :

The migration is now complete.


1. Open the “Computer Management” MMC window you minimized earlier.2. Right click on Disk Management, and select Rescan Disks from the context menu. This might take

a several minutes to complete (with the mouse in the Computer Management window, wait for thehourglass to complete).


2

Figure :

3. Once the rescan completes, verify that you see the Z: drive.


3

Figure :

4. Navigate to Computer Management (Local) > Storage > Data ONTAP® DSM Management.5. In the upper pane, verify it shows the Z: drive as connected to “vserver1”.6. Close the “Computer Management” MMC.


4

5

6

Figure :

The “Computer Management” MMC window closes.

7. On the desktop of Jumphost, launch Windows Explorer.

7

Figure :

Windows Explorer opens.

8. Navigate to the Z: drive, and verify that you can open the “LUN_data.txt” file.9. The file is (intentionally) empty. Add some text to the file and save it, verifying that you can write to the

file.10. Close Windows Explorer.


9

8

10

Figure :

You can now use System Manager, or the CLI, to examine fas01 to verify that the vol2_SAN volume isoffline (although the volume still exists). This exercise is optional, and is not covered here.

The old iSCSI session to fas01 is also still configured on Jumphost. Ordinarily you would likely want todisconnect and remove the iSCSI Initiator configuration for that obsolete session from Jumphost, but itspresence causes no problems in this lab, so this exercise will not bother with that cleanup task.

1.7.3 Task 3: Migrate SnapMirror RelationshipThe objective of this exercise is to transition an NFS volume used by an RHEL server, and that is SnapMirroredto another controller for DR. This exercise uses the same clustered Data ONTAP system as both the primary andsecondary destinations, but even if these destinations were on different clusters the functionality is the same.


Verify the current mount on the RHEL server.

1. Launch PuTTY from the taskbar of Jumphost.


1

Figure :


2. Select the saved session for fas01.3. Click Open.

2

3

Figure :

A PuTTY session opens to fas01.

4. Log in with the username root, and the password Netapp1!.5. Verify that the “snapmirrortest” volume is exported.

fas01> exportfs/vol/vol1_NAS -sec=sys,rw,nosuid/vol/vol2_SAN -sec=sys,rw,nosuid


/vol/vol0 -sec=sys,rw,anon=0/vol/snapmirrortest -sec=sys,rw,nosuidfas02>

6. Open another PuTTY session by clicking on the terminal icon in the upper left corner of your currentPuTTY session window for fas01.

7. Select New Session... from the menu.

6

7

Figure :


8. Select the saved session for rhel1.9. Click Open.


8

9

Figure :

A new PuTTY session window to rhel1 opens.

10. Log in with the username root, and the password Netapp1!.11. Mount the /vol/snapmirrortest volume on fas0 as /mnt/snapmirrortest on rhel1.

[root@RHEL1]# mount 192.168.0.121:/vol/snapmirrortest /mnt/snapmirrortest[root@RHEL1]#

12. Verify that you can see the datafile1 file on this volume.

[root@RHEL1]# ls -al /mnt/snapmirrortestdwrxr-xr-x 3 root root 4096 Jul 11 20:29 .dwrxr-xr-x 3 root root 4096 Sep 3 20:41 ..-wrxr-xr-x 1 root bin 107051776 Aug 29 2013 datafile1dwrxrwxrwx 11 root root 4096 Sep 3 20:00 .snapshot[root@RHEL1]#

13. Minimize the PuTTY session windows for fas01 and rhel1 as you will need them later.


1. If you do not already have the 7-Mode Transition Tool running from a previous exercise, launch it fromthe desktop of Jumphost. (If you already have it open, select the 7-Mode Transition Tool tab in yourbrowser and then skip to step 3.).


1

Figure :

2. Log in as user DEMO\Administrator, with the password Netapp1!.3. Once logged in, click Plan & Design.

3

Figure :

The “Plan Migration” window opens.

4. Select the Copy-Based Transition radio button.5. Click Start Planning.


4

5

Figure :

The “Plan Migration” window closes, and focus returns to the 7MTT browsers window, where a new“(CBT) Untitled Project” tab has opened.

6. If there are not already entries in the 7-Mode Controllers list for fas01 and fas02, or there is not alreadyan entry in the Clustered Data ONTAP Systems list for cluster1, then use the controls in the “EnterDevice Credentials” box to add these systems to their repective lists by using the following values::

• cluster1 Hostname: 192.168.0.101, Username: admin, Password: Netapp1!• fas01 Hostname: 192.168.0.121, Username: root, Password: Netapp1!• fas02 Hostname: 192.168.0.122, Username: root, Password: Netapp1!

7. Click Add after populating the device credentials fields for each of the systems listed in the precedingstep.

8. All 3 controllers now appear in their respective lists.9. On the far right side of the window, click Next. This launches the wizard for the Plan & Design process.


6

7 8

9

Figure :


10. In the “Select 7-Mode Controller” list select the entry for fas01.11. In the “Volume Information” list locate the entry for snapmirrortest, and in that row check the

Transition with Snapmirror Relationship checkbox. This indicates that you are going to transitionboth the primary volume and its SnapMirrored volume.

12. There are now two entries for this volume in the “Volume(s) Selected for Transition Project” listat the bottom of the window, one for the primary volume (snapmirrortest on fas01) and one for itsSnapMirrored copy (snapmirrortest_mirror on fas02), each in its own sub-project. You will configure andtransition these subprojects individually, with the secondary sub-project going first, and the primary sub-project going second.

13. Click the Create Project and Continue button on the right side of the page.


10

11

12

13

Figure :

The “Project Details” window opens.

14. Set the “Project Name” field to SnapMirror.15. Click Save.


14

15

Figure :

The “Project Details” windows closes, and the Plan & Design wizard advances to the “Select Data CopyIP” stage for the SnapMirror_Secondary project.

Figure :

1.7.3.3 Project Configuration – Secondary (Performed first)

The 7-Mode Transition Tool should still be showing the “Select Data Copy IP” stage of the Plan & Design wizardfor the (CBT) SnapMirror_Secondary project. This is the stage where you select which IP addresses on the 7-mode system should be designated as the source for the copy operation.

1. Observe that the title of the current tab in the 7MTT tool has changed to “(CBT) SnapMirror_Secondary”,indicating that you are now working on the sub-project for the secondary volume.


2. The “Data Copy IP” field has been pre-populated with 192.168.0.122, the management IP address offas02. Update this field to specify an address of 192.168.0.155, which is the address of a differentnetwork interface on fas02 that is intended for data access.


1

2

3

Figure :

The Plan & Design wizard advances to the “Select SVM” stage. This is where you select which SVM onthe destination cluster will be the target of the copy operation.

4. In the “Select an SVM” pane on the right, select the checkbox for vserverDR.5. Click the Next button in the middle on the right side of the page.


4

5

Figure :



7. You can modify which target aggregate and which target volume name to use for the volume(s) involvedin this transition. Accept the default values.

8. Click Next in the middle of the far right side of the window.


6

7

8

Figure :

The Plan & Design wizard advances to the “Network Configuration” stage. This is where you select whichIP addresses on the destination cluster will be used for the transition.

There are two ways to specify new LIFs you want to configure on the target vserver. You can eitherchoose to transition existing IPs of the 7-Mode controller, or you can specify details of new LIFs you wantto configure. For this exercise you will create a new LIF.

9. Click Add New LIF.


9

Figure :

The “Add New LIF” window opens.


• “IP Address”: 192.168.0.156• “Netmask”: 255.255.255.0• “Default Gateway”: 192.168.0.1• “Target SVM”: vserverDR• “Target Node”: cluster1-02• “Target port”: e0c

11. Click Save.


10

11

Figure :

The “Add New LIF” window closes, and focus returns to the “Network Configuration” stage of the Plan &Design wizard.

12. A new row describing the LIF you just entered now appears in the lower pane of the window.13. Click the Next button located in the middle of the far right side of the window.

12

13

Figure :

The Plan & Design wizard advances to the “Configure Schedule” stage. This is where you selectwhich time windows are permissible for the SnapMirror operations that will be involved in this transitionproject.


While it is possible to create very detailed and fine-grained schedules with this tool, this exercise usesvery simple schedules. You will create one schedule here that permits round-the-clock transitions.


14

Figure :


15. Name the first schedule DailyAllHours.16. Click Create.


15

16

Figure :


17. Click OK.


17

Figure :


18. The schedule you just created now appears in the list of schedules.19. In the middle of the far right side of the window, click Next.

18

19

Figure :


20. In the “SVM Configuration” pane, uncheck the CIFS section checkbox.21. In the “Volume Configuration” pane, uncheck the CIFS section checkbox.22. Still in the “Volume Configuration” pane, uncheck the SAN section checkbox.

Note: Although CIFS and iSCSI are running on the source controllers, we are only interested inNFS for this lab.

23. Click Save and go to Dashboard on the right side of the window.


2021

22

23

Figure :

The Plan & Design wizard terminates, and the 7-Mode Transition Tool switches over to the MigrationDashboard. This is where the 7-Mode Transition Tool actuallys invokes migrations, but in this exerciseyou are going to focus on just the precheck portion. A precheck runs an analysis of the source, andtargets controllers involved in the current transition project, looking for configuration problems that mightblock the transition.



24

Figure :

A precheck operation status window opens, and tracks the progress of the various checks that thetool is running. Individual checks can return, in increasing order of severity, informational, warning, orerror status results, and in most cases the tool provides suggestions for remediating the issue. Errorstatus results will block a transition completely. Warnings and informational message will not block atransition, but the issues they point out may produce undesireable transition results, so you shouldreview them and consider whether you want to take corresponding action.

It is quite common for the tool to find issues at this stage that require remediation. The specific issuesthe tool will find can vary significantly from system to system, and in the interests of time this labexercise will not produce any errors.

25. The prechecks complete and return an overall operation status of “Successful (With warnings)”.26. Click Close.


25

26

Figure :


27. Notice that the circle for Preparation phase of the transition workflow is green, indicating success.


27

Figure :

1.7.3.4 Project Configuration – Primary

The 7-Mode Transition Tool should still be showing the Migration Dashboard for the SnapMirror_Secondaryproject from the preceding exercise. You next need to configure the project for SnapMirror_Primary.

1. In the left pane of the Migration Dashboard, select the [CBT] SnapMirror_Primary project.2. Click Edit Project > Select Source Volumes.


1

2

Figure :

The 7-Mode Transition Tool window changes to display the “Select Source Volumes” stage of the Plan &Design wizard.

3. Observe that the “Transition with SnapMirror Relationship” checkbox for the “snapmirrortest” volume isalready checked.

4. On the far right side of the page, click Save Project and Continue.


3

4

Figure :

The Plan & Design wizard advances to the “Select Data Copy IP” stage.

5. The “Data Copy IP” field has been pre-populated with 192.168.0.121, the management IP address offas01. Update this field to specify an address of 192.168.0.153, which is the address of a differentnetwork interface on fas01 that is intended for data access.



5

6

Figure :

The Plan & Design wizard advances to the “Select SVM” stage. \

7. In the “Select an SVM” pane on the right, select the checkbox for vserver1.8. Click the Next button in the middle on the right side of the page.


7

8

Figure :

The Plan & Design wizard advances to the “Map Volumes” stage.

9. Accept the default target aggregate and target volume name for this volume.10. Click Next in the middle of the far right side of the window.


9

10

Figure :

The Plan & Design wizard advances to the “Network Configuration” stage.

You will create a new LIF for the primary as well.11. Click Add New LIF.


11

Figure :

The “Add New LIF” window opens.


• “IP Address”: 192.168.0.157• “Netmask”: 255.255.255.0• “Default Gateway”: 192.168.0.1• “Target SVM”: vserver1• “Target Node”: cluster1-01• “Target port”: e0c

13. Click Save.


12

13

Figure :

The “Add New LIF” window closes, and focus returns to the “Network Configuration” stage of the Plan &Design wizard.

14. A new row describing the LIF you just entered now appears in the lower pane of the window.15. Click the Next button located in the middle of the far right side of the window.

14

15

Figure :

The Plan & Design wizard advances to the “Configure Schedule” stage.

You will create one schedule for the primary that permits round-the-clock transitions.



16

Figure :


17. Name the first schedule DailyAllHours.18. Click Create.


17

18

Figure :


19. Click OK.


19

Figure :


20. The schedule you just created now appears in the list of schedules.21. In the middle of the far right side of the window, click Next.

20

21

Figure :

The Plan & Design wizard advances to the “Plan Configuration” stage. Here you will uncheck the samecheckboxes you unchecked for the secondary.

22. In the “SVM Configuration” pane, uncheck the CIFS section checkbox.23. In the “Volume Configuration” pane, uncheck the CIFS section checkbox.24. Still in the “Volume Configuration” pane, uncheck the SAN section checkbox.25. Click Save and go to Dashboard on the right side of the window.


2223

24

25

Figure :

The Plan & Design wizard terminates, and the 7-Mode Transition Tool switches over to the MigrationDashboard.



26

Figure :

A precheck operation status window opens, and tracks the progress of the various checks that the toolis running.

27. The prechecks complete, and return an overall operation status of “Successful (With warnings)”.28. Click Close.


27

28

Figure :


29. Notice that the circle for Preparation phase of the transition workflow is green, indicating success.


29

Figure :

1.7.3.5 Perform Migration – Secondary

The 7-Mode Transition Tool should still be showing the Migration Dashboard for the SnapMirror_Primary projectfrom the preceding exercise.

1. In the left pane of the Migration Dashboard, select the [CBT] SnapMirror_Secondary project.2. Click Start Baseline.


1

2

Figure :

A “Warning” window opens that recommends you address all the precheck warning before you proceed.3. Click Yes.

3

Figure :

The “Warning” window closes, and the “Start Baseline Operation Status” window opens, and runs theprechecks again.




4

Figure :


The lower pane of the Migration Dashboard now opens to the “Volumes” tab, and displays the progressof the baseline transfer. The baseline transfer will be subject to the schedule and bandwidth restrictionsyou set up for your transition project. Depending on how restrictive those restrictions were, this couldmean the baseline transfer may not actually start until a later time. Additionally, depending on how largeyour data footprint is, it may takes hours or days for the baseline transfer to complete. In this lab exercisethe data footprint is very small (just 1 file) and the schedule is unrestricted, so the baseline transfershould complete in moments.

5. Periodically click Refresh until the Baseline Data Copy circle turns green.

Note: In the interest of saving time, this exercise will not use “Test Mode” to verify the precutoverconfiguration. If you are interested in seeing that feature, the “Migrate NAS Volumes” task in thislab guide includes that functionality.

6. Click Apply Configuration.


5

6

Figure :


7. Click Continue.

7

Figure :




9. Click Close.

8

9

Figure :


10. The circle for the Precutover phase of the transition has turned green.

Note: While the dashboard indicates that you are technically ready to perform a storagecutover, in practice you will first want to perform an incremental update so you can minimize theamount of data you will have to transfer during the actual storage cutover step.



10

11

Figure :


12. Click Continue.

12

Figure :




13

Figure :


Note: In a production environment you would now stop client activity to the volumes in themigration project so that there will be no client-initiated corruption to the volume, as the cutoveris a disruptive process. However, since this lab does not contain any active clients, you will skipthis step for this exercise.

14.Click Complete Transition.

14

Figure :




15

Figure :



16

17

Figure :



19. Click Close.


18

19

Figure :



20

Figure :

The migration of the secondary is now complete.


1.7.3.6 Perform Migration - Primary

The 7-Mode Transition Tool should still be showing the Migration Dashboard for the SnapMirror_Secondaryproject from the preceding exercise.

1. In the left pane of the Migration Dashboard, select the [CBT] SnapMirror_Primary project.2. Click Start Baseline.

1

2

Figure :

A “Warning” window opens that recommends you address all the precheck warnings before you proceed.3. Click Yes.

3

Figure :

The “Warning” window closes, and the “Start Baseline Operation Status” window opens and runs theprechecks again.



4

Figure :


5. Periodically click Refresh until the Baseline Data Copy circle turns green.6. Click Apply Configuration.

56

Figure :



7. Click Continue.

7

Figure :


8. The “Operation Status” will show “Running...” until the operation completes, at which point it changes to“Successful (With warnings)”.

9. Click Close.


8

9Figure :



10

Figure :



11. Click Continue.

11

Figure :



12

Figure :


Disconnect any clients from fas01 before starting the cutover.13. Open up the PuTTY session to rhel1 that you minimized earlier. If that PuTTY session is no longer

available, open a new PuTTY session to rhel1 and log in as the user root with the password Netapp1!.14. Unmount the NFS mount of /vol/snapmirrortest from fas01.

[root@RHEL1]# umount /mnt/snapmirrortest[root@RHEL1]#

Keep the PuTTY session to RHEL1 open, as you will need it again later.

15.In the “7-Mode Transition Tool” window, click Complete Transition.


15

Figure :



16

Figure :




17

18

Figure :



20. Click Close.

19

20

Figure :




21

Figure :

The migration of the primary is now complete.


1. Switch to the PuTTY session to rhel1 that you should still have open from the previous exercise. If thatPuTTY session is no longer available, open a new PuTTY session to rhel1, and log in as the user rootwith the password Netapp1!.

2. NFS mount the /vol/snapmirrortest volume from vserver1.

Note: This mount command uses a different IP address (192.268.0.157) than you used whenyou earlier mounted the volume from fas01 (192.168.0.121).

[root@RHEL1]# mount 192.168.0.157:/vol/snapmirrortest /mnt/snapmirrortest[root@RHEL1]#

3. Verify the contents of the mounted NFS volume, and that it is writeable.

[root@RHEL1]# cd /mnt/snapmirrortest[root@RHEL1]# ls -aldwrxr-xr-x 3 root root 4096 Jul 11 20:29 .dwrxr-xr-x 3 root root 4096 Sep 3 20:41 ..-wrxr-xr-x 1 root bin 107051776 Aug 29 2013 datafile1dwrxrwxrwx 11 root root 4096 Sep 3 20:00 .snapshot[root@RHEL1]# touch newfile[root@RHEL1]# ls -aldwrxr-xr-x 3 root root 4096 Jul 11 20:29 .dwrxr-xr-x 3 root root 4096 Sep 3 20:41 ..-wrxr-xr-x 1 root bin 107051776 Aug 29 2013 datafile1-wrxr-xr-x 1 root bin 107051776 Sep 3 20:45 newfiledwrxrwxrwx 11 root root 4096 Sep 3 20:00 .snapshot[root@RHEL1]#

4. Exit the PuTTY session to rhel1.

[root@RHEL1]# exit

You can now use System Manager or the CLI to:

• Examine fas01 to see that the /vol/snapmirrortest volume is offline on that controller.• Examine fas02 to see the the /vol/snapmirrortest_mirror volume is offline there too.


• Examine cluster1 to verify that the vservers, volumes, LIFs, and snapmirror relationships areall present and correct.

However, in the interest of brevity, these activities are not covered in this lab guide, and are left to yourdiscretion to perform.

1.8 Logging in 7MTT and Collecting 7MTT Logs

The 7-Mode Transition Tool should still be showing the Migration Dashboard from whichever transition exerciseyou chose to run in this lab.

1. At the top of the 7MTT window, click Logs.

The 7MTT tool displays the “Collect Transition Logs” page.

Note: While you can gather logs for individual transitions that you ran during this lab (by clickingthe download icons on each separate line), this exercise will have you download all the logs in asingle operation.

2. Click Collect All Logs

1

2

Figure :

The “Transition Logs” window opens, and prompts you whether you want to download the logs.

3. Click Yes.


3

Figure :

The “Transition Logs” window closes, and a Firefox dialog opens asking what you want to do with thefile.

4. Click OK to accept the defaults and open the file with Windows Explorer.

4

Figure :

The Firefox dialog closes, and Windows Explorer opens.

5. Windows Explorer displays the various folders that comprise the log bundle.


5

Figure :

Feel free to explore the details of the various log files in the bundle.

1.9 Summary

You have completed two types of transition in this lab:

• Transition standalone volumes, with and without LUNs.• Transition volumes along with their DR relationship.

You have learned how to perform the following tasks:

• Collected information about your existing environment and assessed the differences in features andfunctionalities currently in use between Data ONTAP 7-Mode and clustered Data ONTAP.

• Choose volumes and created transition projects.• Configured the subprojects.• Started and cutover the transition.

After completing this lab, you should be able to do the following:

• Use 7MTT to gather information about your existing environment• Generate an assessment on 7-Mode DATA ONTAP controller to see the differences in features and

functionalities currently in use between Data ONTAP 7-Mode and clustered Data ONTAP.• Complete a migration of both standalone volumes and SnapMirror relationships using the 7MTT.

1.10 References

The following references were used to create this lab guide.

• 7MTT v2.0 Product Documentation• http://mysupport.netapp.com/documentation/docweb/index.html?productID=61851

http://mysupport.netapp.com/documentation/docweb/index.html?productID=61851


• TR-4052: Successfully Transitioning to Clustered Data ONTAP• http://www.netapp.com/us/media/tr-4052.pdf

1.11 Version History

Version Date Document Version History

Version 1.3 Oct 2014 Update to 7MTT v2.0

Version 1.1 July 2014 Updated to 7MTT v1.3

Version 1.0 May 2013 Initial Release – 7MTT v1.2

Version 2.0 September 2014 Initial Release – 7MTT v2.0 (Insight 2014)

Version 2.1 September 2015 Initial Release – 7MTT v2.1 (Insight 2015)

https://fieldportal.netapp.com/Core/DownloadDoc.aspx?documentID=71405&contentID=74887

http://www.netapp.com/us/media/tr-4052.pdf

Refer to the Interoperability Matrix Tool (IMT) on the NetApp Support site to validate that the exactproduct and feature versions described in this document are supported for your specific environment.The NetApp IMT defines the product components and versions that can be used to constructconfigurations that are supported by NetApp. Specific results depend on each customer's installation inaccordance with published specifications.

NetApp provides no representations or warranties regarding the accuracy, reliability, or serviceability of anyinformation or recommendations provided in this publication, or with respect to any results that may be obtainedby the use of the information or observance of any recommendations provided herein. The information in thisdocument is distributed AS IS, and the use of this information or the implementation of any recommendations ortechniques herein is a customer’s responsibility and depends on the customer’s ability to evaluate and integratethem into the customer’s operational environment. This document and the information contained herein may beused solely in connection with the NetApp products discussed in this document.

Go further, faster®

© 2016NetApp, Inc. All rights reserved. No portions of this document may be reproduced without prior written consentof NetApp, Inc. Specifications are subject to change without notice. NetApp, the NetApp logo, Data ONTAP®,ONTAP®, OnCommand®, SANtricity®, FlexPod®, SnapCenter®, and SolidFire® are trademarks or registeredtrademarks of NetApp, Inc. in the United States and/or other countries. All other brands or products are trademarks orregistered trademarks of their respective holders and should be treated as such.

http://support.netapp.com/matrix/mtx/login.do

Migrating to NetApp ONTAP Using the 7-Mode Transition Tool … · Migrating to NetApp ONTAP Using...

Documents

Transcript of Migrating to NetApp ONTAP Using the 7-Mode Transition Tool … · Migrating to NetApp ONTAP Using...