The Netapp 7MTT software helps you easily migrate from Data Ontap 7-Mode to Clustered Data Ontap via an easy to use step-by-step wizard.
In this tutorial we will walk through migrating an iSCSI lun that is attached to a Windows 2012 R2 server containing an SQL database on 7-Mode to Clustered Data Ontap 8.3.2
The latest version of the Netapp 7MTT software is version 3 and can be found here:
Netapp 7MTT v3
If you are familiar with previous versions where you were required to install either Copy-Based Transition or Copy-Free Transition, you will be happy in version 3 that this is no longer the case and the one installation contains both CBT and CFT.
Netapp 7-Mode Transition Tool (7MTT)
After installing the 7-Mode Transition Tool, click on the icon to launch it.
Click on Storage Systems at the top and enter in your 7-mode node ip followed by the username and password. Click Add
Enter in your Cluster IP, username and password for the c-mode system and click Add.
Click on the Home tab at the top left and select Copy-Based Transition. Click on the Start Planning button.
Your 7-mode and c-mode controllers are already populated. Click Next.
Select the source 7-mode volume by clicking on the box under the Transition as stand-alone column. Click Next.
You will receive a warning, as we are migrating to a c-mode system running 8.3.2 we can click Ok.
Give the project a name and you can either create a new group or use the default. This is useful to group projects together. Click Save.
Your 7-mode management IP will already be pre-populated here. Double check to make sure it is the correct IP. Click Next.
In this window we will select the target SVM on the Netapp c-mode system. In my example the SVM is called SVM1. Ensure that the box is ticked next to your destination SVM. Click Next.
We can now create the destination volume on the Netapp c-mode system. Select the destination aggregate and type in a Target Volume Name. I like to use the clustered ontap mount policy and I recommend you select the same otherwise it will append /vol to your namespace mount points. In the example below, I show you what the Target Volume Path would look like if you select the Preserve 7-Mode Mount paths
In this example, I show you what it looks like with the Clustered Data Ontap volume name mount policy. As you can see it’s much cleaner. Click Next.
Now I will create a new iSCSI lif on the Clustered Data Ontap system. Click Save once you are done.
We are now going to configure the replication schedule. This is important as it gives us the flexibility to either cutover straight away or continue replicating the data until we are ready to cut over. In my lab I have accepted the defaults. Click create.
Here are a bunch of options that we can migrate across from 7-mode to c-mode. I have unticked most of them as I’m only interested in SAN and Snapshot schedules. When you are finished click Save and go to Dashboard.
We can now run a pre-check before any configuration is done. Click Run Precheck.
I have a few errors that have popped up that I need to fix before moving on. Untick Warning and Informational at the bottom to only see Errors.
First up we’ll create the Intercluster LIFs on the Clustered Data Ontap system.
Next we’ll allow SVM1 to snapmirror from our Data Ontap 7-mode system.
Lastly, we’ll turn the Netapp 7-mode volume option no_i2p to off on our volume iscsi.
We can now re-run the pre check and as you can see it is now successful.
The Run Precheck circle is now green and we can move onto Starting the Baseline.
Click Start Baseline. We have fixed up all the warnings so we can safely click Yes.
The baseline snapmirror is now transferring.
We can also see this via the Netapp Clustered Data Ontap command line by typing in snapmirror show.
Now it comes time to apply the configuration. We have an option to Test the destination and ensure everything is working. The Test Mode involves a volume clone process in the back-end. In my lab I will move straight onto clicking Apply Configuration.
After clicking Apply Configuration the Apply Configuration(Precutover) window pops up. I will untick the Apply configuration in test mode option and click continue.
The next pop-up window lists all the steps that were involved in the pre-cutover phase.
Snapmirror has completed another update.
We can now click on Complete Transition. A Warning window pops up ensuring you address all warnings before continuing. Click yes.
One last window pops up giving you the option to take the source volume offline once the transition is complete. I will leave this selected. Don’t click Continue yet.
I have connected via remote desktop to my SQL server. Shut down all the SQL services and disconnect from the Netapp 7-mode iSCSI lun.
We can now click Continue on the Complete Transition Window. Once the transition is complete you will see a summary of steps along with a Operation Status of Successful.
All phases of the transition are now green. We can sign out of the Netapp 7MTT tool.
Back over to our SQL server, I will go back into the iSCSI initiator and add the target IP address of the Netapp Clustered Data Ontap LIF.
Within Disk Manager we can see the disk appear as offline. Right click the disk and select Online.
The disk is now online as E: and we can see our SQL database files within the drive.
One last check within Microsoft SQL Management Studio. The vum database is online and healthy. Thank you Netapp 7MTT.
The post Netapp 7MTT iSCSI LUN Migration Example appeared first on SYSADMINTUTORIALS IT TECHNOLOGY BLOG.