Skip to main content
ONTAP MetroCluster

Workflow for nondisruptive MetroCluster transition

Contributors netapp-aoife NetAppZacharyWambold
PDFs

You must follow the specific workflow to ensure a successful nondisruptive transition. Choose the workflow for your configuration:

Four-node FC configuration transition workflow

The transition process begins with a healthy four-node MetroCluster FC configuration.

transition dr group 1 fc nodes

The new MetroCluster IP nodes are added as a second DR group.

transition dr groups fc and ip

Data is transferred from the old DR group to the new DR group, and then the old nodes and their storage are removed from the configuration and decommissioned. The process ends with a four-node MetroCluster IP configuration.

transition dr group 2 ip

Eight-node FC configuration transition workflow

The transition process begins with a healthy eight-node MetroCluster FC configuration.

mcc dr group c1

The new MetroCluster IP nodes are added as a third DR group.

mcc dr group c2

Data is transferred from DR_group_1-FC to DR_group_1-IP, and then the old nodes and their storage are removed from the configuration and decommissioned.

Note If you want to transition from an eight-node FC configuration to a four-node IP configuration, you must transition all the data in DR_group_1-FC and DR_group_2-FC to the new IP DR group (DR_group_1-IP). You can then decommission both FC DR groups. After the FC DR groups have been removed, the process ends with a four-node MetroCluster IP configuration.
mcc dr group c8

Add the remaining MetroCluster IP nodes to the existing MetroCluster configuration. Repeat the process to transfer data from the DR_group_2-FC nodes to the DR_group_2-IP nodes.

mcc dr group c7

After removing DR_group_2-FC, the process ends with an eight-node MetroCluster IP configuration.

mcc dr group c6

Transition process workflow

You will use the following workflow to transition the MetroCluster configuration.

workflow 4n transition nondisruptive