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
NETAPP_CMODE::> snapmirror show OR snapmirror show -destination-path NETAPP_CMODE:vmware_datastore1
NETAPP_CMODE::> snapmirror update -destination-path NETAPP_CMODE:vmware_datastore1
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
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
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.
To be able to move luns across from 7-mode to c-mode you must use NetApp’s 7MTT tool. Click here to read my article on how to use 7MTT
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
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.
Can you have a setup where source7mode64 —TDP– > destinationCmode64 —DP–> VserverPeerCmode ?
Hi Ashutosh, first question I have is are your snapshots on the source7mode64 volume 32-bit or 64-bit ?
Last time i tried this it didn’t work. Cant have a destination volume of a TDP relationship as a source for another snapmirror relationship (CDOT->CDOT)
Could we snapmirror (snapvault) using the transition from 8.2.x (7 mode) to 9.5.x (Cdot) ?
With the -type TDP options ?
Wanted to update my answer a bit. Technically you CAN do this however you can only have one of the snapmirror relationships active at any given time. So basically you would baseline the TDP relationship to the first CDOT system. Quiesce/break the mirror and then you would be allowed to snapmirror to the peer CDOT system. The use case for this is very small, but I did run into needing to to this to finish a migration.
This generally wouldn’t be used as an active snapmirror chain for say a low RPO DR scenario.