Skip to main content
ONTAP MetroCluster

Choosing a system refresh method

Contributors netapp-aoife netapp-folivia netapp-martyh
PDFs

The system refresh procedure you use depends on the platform model, and type of MetroCluster configuration. Refresh procedures apply to the controllers and the storage shelves. In the refresh procedures, new controllers and shelves are added to the MetroCluster configuration, creating a second DR group, and then data is nondisruptively migrated to the new nodes. The original controllers are then retired.

Supported MetroCluster IP tech refresh combinations

  • You must complete the tech refresh procedure before adding a new load.

  • All nodes in the MetroCluster configuration must be running the same ONTAP version. For example, if you have an eight-node configuration, all eight nodes must be running the same ONTAP version.

  • Do not exceed any object limits of the 'lower' of the platforms in the combination. Apply the lower object limit of the two platforms.

  • If the target platform limits are lower than the MetroCluster limits, you must reconfigure the MetroCluster to be at, or below, the target platform limits before you add the new nodes.

  • Refer to the Hardware universe for platform limits.

Supported AFF and FAS MetroCluster IP tech refresh combinations

The following table shows the supported platform combinations for refreshing an AFF or FAS system in a MetroCluster IP configuration:

MetroCluster IP tech refresh combinations

Note 1: This combination requires ONTAP 9.13.1 or later.

Supported ASA MetroCluster IP tech refresh combinations

The following table shows the supported platform combinations for refreshing an ASA system in a MetroCluster IP configuration:

MetroCluster IP ASA tech refresh combinations

Supported MetroCluster FC tech refresh combinations

  • You must complete the tech refresh procedure before adding a new load.

  • All nodes in the MetroCluster configuration must be running the same ONTAP version. For example, if you have an eight-node configuration, all eight nodes must be running the same ONTAP version.

  • Do not exceed any object limits of the 'lower' of the platforms in the combination. Apply the lower object limit of the two platforms.

  • If the target platform limits are lower then the MetroCluster limits, you must reconfigure the MetroCluster to be at, or below, the target platform limits before you add the new nodes.

  • Refer to the Hardware universe for platform limits.

Supported AFF and FAS MetroCluster FC tech refresh combinations

The following table shows the supported platform combinations for refreshing an AFF or FAS system in a MetroCluster FC configuration:

metrocluster fc tech refresh
Supported ASA MetroCluster FC tech refresh combinations

The following table shows the supported platform combinations for refreshing an ASA system in a MetroCluster FC configuration:

Source MetroCluster FC platform Destination MetroCluster FC platform Supported?

ASA A400

ASA A400

Yes

ASA A900

No

ASA A900

ASA A400

No

ASA A900

Yes

Choose a refresh procedure

Choose the refresh procedure for your configuration from the following table:

Refresh method Configuration type ONTAP version Procedure

  • Method: Expand the MetroCluster configuration and then remove the old nodes

Four-node FC

9.6 and later

Link to procedure

  • Method: Expand the MetroCluster configuration and then remove the old nodes

Four-node IP

9.8 and later

Link to procedure