Limitations when the MetroCluster configuration is in switchover

10/07/2026 Contributors

When the system is in switchover, NetApp recommends that you avoid performing certain operations.

The following operations are not recommended when the system is in switchover and you should only perform them under guidance from NetApp support:

Creating or deleting aggregates
Creating or deleting volumes (including encrypted volumes)
Creating or deleting SVMs
Creating or deleting LIFs
Adding or removing disks (only if you are replacing them as part of a recovery procedure)
Performing configuration changes to SnapMirror SVM DR
Modifying existing broadcast domains or creating new broadcast domains
Modifying network subnets

Hardware replacement in switchover

Use the following procedures to replace controller hardware when the system is in switchover:

If you need to replace a controller of the same type, at the site not in switchover, follow the procedure to Recover from a multi-controller or storage failure.
- If you need to replace the controller modules and chassis while the nodes are switched over at the surviving site, shut down both controllers and then perform the procedure to Recover from a multi-controller or storage failure.
If you need to replace a controller with a different type of controller, follow the procedure for your configuration in Choose a controller upgrade procedure.
- If your system is in switchover because of a controller failure or if you experience a controller failure while in switchover, you must first replace the controller hardware, perform a switchback, and then perform a controller upgrade:
  1. To replace the controller hardware and perform the switchback, follow Recover from a multi-controller or storage failure.
  2. After you have replaced the hardware, perform a controller upgrade using the procedures in Choose a controller upgrade procedure.

Beginning with ONTAP 9.20.1, storage limits can be configured for SVMs that are part of a MetroCluster IP configuration.

You must ensure that your MetroCluster configuration does not exceed the limits for your platform listed in the Hardware Universe.

During normal operation (not in switchover), you can change the storage limit configuration only on the sync-source SVM. You cannot enable, disable, or modify storage limits on the sync-destination SVM.
While in switchover, the following restrictions apply to the sync-destination SVM:
- You can't use the vserver modify -storage-limit command to enable or disable the storage limit on the sync-destination SVM. That is, you can't change the value from 0 to a non-zero value, or from a non-zero value to 0. The command fails with the following error:
  
  This operation is not permitted on a Vserver that is configured as the destination of a MetroCluster Vserver relationship
- You can still change the storage limit from one non-zero value to another (for example, from 100TB to 200TB). This new value is retained across switchback.
- To enable or disable the storage limit, wait until switchback completes, then make the change on the sync-source SVM. The value is then replicated to the sync-destination SVM.

For more information, refer to Manage ONTAP SVM capacity