Skip to main content
NetApp adopts Microsoft’s Business-to-Customer (B2C) Identity Management
Effective December 3 - NetApp adopts Microsoft’s Business-to-Customer (B2C) identity management to simplify and provide secure access to NetApp resources. For accounts that did not pre-register (prior to Dec 3) access to your NetApp data may take up to 1 hour as your legacy NSS ID is synchronized to the new B2C identity. To learn more, Read the FAQ and Watch the video. Need assistance? Complete this form and select “Registration Issue” as the Feedback Category. 
NetApp Knowledge Base

How to move mroot to a new root aggregate in a 2-node Clustered MetroCluster with Switchover

Views:
944
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
metrocluster
Last Updated:

Applies to

  • MetroCluster FC
  • 2-node
  • ONTAP 9

Description

In a 2-node clustered Data ONTAP MetroCluster configuration, the root volume can be moved to a new root aggregate non-disruptively through the use of Switchover.
This article describes the procedure to be followed to move mroot to a new root aggregate in a 2-node Clustered MetroCluster with Switchover.

The root vol migrate feature in ONTAP 9.0 is not possible in 2-node MetroCluster