Which operation migrates a MetroCluster from FC to IP architecture?

The process of migrating an existing MetroCluster FC configuration to a MetroCluster IP configuration is officially termed a "MetroCluster transition." This is a specific, documented, non-disruptive procedure that involves adding the new IP switches, configuring the IP interfaces, and then systematically moving the backend connectivity from the FC fabric to the new IP network. The term "transition" is used by NetApp to describe this specific migration path.

B. A MetroCluster rebuild is an operation performed to re-establish a mirrored relationship after a site disaster or component failure, not for changing interconnect types.

C. MetroCluster compression is not a valid operation; compression is a storage efficiency feature applied to data, not the cluster architecture itself.

D. A MetroCluster restore involves recovering data from backups and is unrelated to migrating the underlying interconnect infrastructure from FC to IP.

1. NetApp, "Transitioning from a MetroCluster FC to a MetroCluster IP configuration," ONTAP 9.8 Documentation Center. The title of the official guide for this procedure is "Transition from MetroCluster FC to MetroCluster IP configurations," confirming the terminology.

2. NetApp, "MetroCluster IP Installation and Configuration Guide," ONTAP 9.8, Document ID: 215-14322A0, Page 21, Section: "Transitioning from MetroCluster FC to MetroCluster IP configurations." This section introduces the procedure and refers to it as a transition.