When to migrate root volumes to a new destination
You might need to move root volumes to another root aggregate within a two-node or four-node MetroCluster configuration.
Migrating root volumes within a two-node MetroCluster configuration
To migrate root volumes to a new root aggregate within a two-node MetroCluster configuration, you should refer to the procedure in the following Knowledgebase article. This procedure shows you how to non-disruptively migrate the root volumes during a MetroCluster switchover operation. This procedure is slightly different than the procedure used on a four-node configuration.
Migrating root volumes within a four-node MetroCluster configuration
To migrate root volumes to a new root aggregate within a four-node MetroCluster configuration, you can use the system node migrate-root command while meeting the following requirements.
You can use system node migrate-root to move root aggregates within a four-node MetroCluster configuration.
All root aggregates must be mirrored.
You can add new shelves on both sites with smaller SSDs to host the root aggregate.
You must check the SSD limits that the platform supports before attaching new disks.
If you move the root aggregate to smaller disks, you need to accommodate the minimum root volume size of the platform to ensure all core files are saved.
|The four-node procedure can also be applied to an eight-node configuration.|