Netapp Snapmirror 7-Mode to Cluster Mode
To transition your volumes from Data Ontap 7-Mode to Data Ontap Clustered Mode or C-Mode you can use the following steps.
In the following example the Netapp 7-mode SAN is called NETAPP_7MODE (192.168.2.10) and the Netapp Clustered Ontap system is called NETAPP_CMODE (192.168.1.10).
Both are running Data Ontap 8.2
Creating a Netapp Peer Transition
NETAPP_CMODE::> vserver peer transition create -local-vserver NETAPP_CMODE -src-filers-name NETAPP_7MODE
Transition peering created
Create a Destination Volume
NETAPP_CMODE::> volume create -volume vmware_datastore1 -aggregate aggr1 -size 100GB -type DP
[Job 16] Job succeeded: Successful
Create an Netapp Intercluster LIF
NETAPP_CMODE::> network interface create -vserver NETAPP_CMODE -lif intcl_lif1 -role intercluster -home-node NETAPP_CMODE -home-port a0a-10 -address 192.168.1.10 -netmask 255.255.255.0
NETAPP_CMODE::> network routing-groups route create -vserver NETAPP_CMODE -routing-group i192.168.1.0/24 -destination 0.0.0.0/0 -gateway 192.168.1.1
Network Ping Test
NETAPP_CMODE::> network ping -lif intcl_lif1 -lif-owner NETAPP_CMODE -destination 192.168.2.10
192.168.2.10 is alive
Create a Netapp Snapmirror Relationship using TDP (Transition Relationship)
NETAPP_CMODE::> snapmirror create -source-path NETAPP_7MODE:vmware_datastore1 -destination-path NETAPP_CMODE:vmware_datastore1 -type TDP
Operation succeeded: snapmirror create the relationship with destination NETAPP_CMODE:vmware_datastore1
Initialize the Snapmirror
NETAPP_CMODE::> snapmirror initialize -destination-path NETAPP_CMODE:vmware_datastore1
Operation is queued: snapmirror initialize of destination NETAPP_CMODE:vmware_datastore1
Snapmirror Status
NETAPP_CMODE::> snapmirror show OR snapmirror show -destination-path NETAPP_CMODE:vmware_datastore1
Snapmirror Update
NETAPP_CMODE::> snapmirror update -destination-path NETAPP_CMODE:vmware_datastore1
Snapmirror Quiesce
NETAPP_CMODE::> snapmirror quiesce -destination-path NETAPP_CMODE:vmware_datastore1
Snapmirror Resume (From Quiesced State)
NETAPP_CMODE::> snapmirror resume -destination-path NETAPP_CMODE:vmware_datastore1
Snapmirror break
NETAPP_CMODE::> snapmirror break -destination-path NETAPP_CMODE:vmware_datastore1
Snapmirror Job Schedule
NETAPP_CMODE::> job schedule cron create -name Every15mins -minute 15
NETAPP_CMODE::> snapmirror modify -destination-path NETAPP_CMODE:vmware_datastore1 -schedule Every15mins
GOTCHA’S
7-Mode iSCSI or FCP Luns – If your source 7-mode volume contains iSCSI or FCP luns, these cannot be transitioned to a Clustered Data Ontap SAN. You will see this error in the SAN log:
wafl.voltrans.lun.exists: Volume [email protected]:a0cc5791-fd70-11e2-9f1f-123478563412 contains 7-Mode LUNs. It cannot be transitioned to Cluster-Mode.
You must manually copy the data or use an imaging software such as Shadow Protect or Symantec Backup and Imaging Software for example.
FS_FIXED_SIZE – Once your snapmirror has completed and you quiesce and break it the options fs_fixed_size is set to on by default. In cluster mode it prohibits you to run the command vol options <vol_name> fs_fixed_size off, so you must run the following command:
vol modify -vserver <vserver_name> -volume <volume_name> -filesys-size-fixed false
If you have any technical questions about this tutorial or any other tutorials on this site, please open a new thread in the forums and the community will be able to help you out.
Disclaimer:
All the tutorials included on this site are performed in a lab environment to simulate a real world production scenario. As everything is done to provide the most accurate steps to date, we take no responsibility if you implement any of these steps in a production environment.