Please follow & like us :)

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 ( and the Netapp Clustered Ontap system is called NETAPP_CMODE (

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 -netmask

NETAPP_CMODE::> network routing-groups route create -vserver NETAPP_CMODE -routing-group i192.168.1.0/24 -destination -gateway

Network Ping Test

NETAPP_CMODE::> network ping -lif intcl_lif1 -lif-owner NETAPP_CMODE -destination 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


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.


  1. Can you have a setup where source7mode64 —TDP– > destinationCmode64 —DP–> VserverPeerCmode ?

  2. Could we snapmirror (snapvault) using the transition from 8.2.x (7 mode) to 9.5.x (Cdot) ?
    With the -type TDP options ?

Leave a Reply

Your email address will not be published.



This site uses Akismet to reduce spam. Learn how your comment data is processed.