Scribd
Upload
410 views2 pages

Netapp Snapmirror 7-Mode To Cluster Mode

This document outlines the steps to transition volumes from a Netapp 7-Mode system to a Clustered Mode (C-Mode) system using Snapmirror. This involves creating a peer transition, destination volume, intercluster LIF, Snapmirror relationship in transition mode, initializing and updating the Snapmirror, and optionally setting up scheduled Snapmirror updates. It notes that LUNs cannot be transitioned and the fs_fixed_size option needs to be disabled after transition.

Uploaded by

123usg
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
410 views2 pages

Netapp Snapmirror 7-Mode To Cluster Mode

This document outlines the steps to transition volumes from a Netapp 7-Mode system to a Clustered Mode (C-Mode) system using Snapmirror. This involves creating a peer transition, destination volume, intercluster LIF, Snapmirror relationship in transition mode, initializing and updating the Snapmirror, and optionally setting up scheduled Snapmirror updates. It notes that LUNs cannot be transitioned and the fs_fixed_size option needs to be disabled after transition.

Uploaded by

123usg
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 2

Netapp Snapmirror 7-Mode to Cluster Mode

To transition your volumes from Data Ontap 7-Mode to Data Ontap Clustered Mode o
r 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 -srcfilers-name NETAPP_7MODE
Transition peering created
Create a Destination Volume
NETAPP_CMODE::> volume create -volume vmware_datastore1 -aggregate aggr1 -size 1
00GB -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.1
0 -netmask 255.255.255.0
NETAPP_CMODE::> network routing-groups route create -vserver NETAPP_CMODE -routi
ng-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 -destinatio
n 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 -d
estination-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_data
store1
Operation is queued: snapmirror initialize of destination NETAPP_CMODE:vmware_da
tastore1
Snapmirror Status
NETAPP_CMODE::> snapmirror show OR snapmirror show -destination-path NETAPP_CMOD
E:vmware_datastore1
Snapmirror Update
NETAPP_CMODE::> snapmirror update -destination-path NETAPP_CMODE:vmware_datastor
e1
Snapmirror Quiesce

NETAPP_CMODE::> snapmirror quiesce -destination-path NETAPP_CMODE:vmware_datasto


re1
Snapmirror Resume (From Quiesced State)
NETAPP_CMODE::> snapmirror resume -destination-path NETAPP_CMODE:vmware_datastor
e1
Snapmirror break
NETAPP_CMODE::> snapmirror break -destination-path NETAPP_CMODE:vmware_datastore
1
Snapmirror Job Schedule
NETAPP_CMODE::> job schedule cron create -name Every15mins -minute 15
NETAPP_CMODE::> snapmirror modify -destination-path NETAPP_CMODE:vmware_datastor
e1 -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 vmware_datastore1@vserver:a0cc5791-fd70-11e2-9f
1f-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 Protec
t or Symantec Backup and Imaging Software for example.
FS_FIXED_SIZE
Once your snapmirror has completed and you quiesce and break it th
e options fs_fixed_size is set to on by default. In cluster mode it prohibits yo
u to run the command vol options fs_fixed_size off, so you must run the followin
g command:
vol modify -vserver -volume -filesys-size-fixed false

You might also like