You can change the ownership of an aggregate only between the nodes within an HA pair.
About this task
- Because volume count limits are validated programmatically during aggregate relocation operations, it is not necessary to check for this manually.
If the volume count exceeds the supported limit, the aggregate relocation operation fails with a relevant error message.
- You should not initiate aggregate relocation when system-level operations are in progress on either the source or the destination node; likewise, you should not start these operations during the aggregate relocation.
These operations can include the following:
- Another aggregate relocation operation
- Disk ownership changes
- Aggregate or volume configuration operations
- Storage controller replacement
- Data ONTAP upgrade
- Data ONTAP revert
- If you have a MetroCluster configuration, you should not initiate aggregate relocation while disaster recovery operations (switchover, healing, or switchback) are in progress.
- If you have a MetroCluster configuration and initiate aggregate relocation on a switched-over aggregate, the operation might fail because it exceeds the DR partner's volume limit count.
- You should not initiate aggregate relocation on aggregates that are corrupt or undergoing maintenance.
- For All-Flash Optimized FAS80xx-series systems, both nodes in the HA pair must have the All-Flash Optimized personality enabled.
Because the All-Flash Optimized configuration supports only SSDs, if one node in the HA pair has HDDs or array LUNs (and therefore, is not configured with the All-Flash Optimized personality), you cannot perform an aggregate relocation from that node to the node with the All-Flash Optimized personality enabled.
- If the source node is used by an Infinite Volume with SnapDiff enabled, you
must perform additional steps before initiating the aggregate relocation and then perform the relocation in a specific manner.
You must ensure that the destination node has a namespace mirror constituent and make decisions about relocating aggregates that include namespace constituents.
Clustered Data ONTAP 8.3 Infinite Volumes Management Guide
- Before initiating the aggregate relocation, you should save any core dumps on the source and destination nodes.
- View the aggregates on the node to confirm which aggregates to move and ensure they are online and in good condition:storage aggregate show -node source-node
The following command shows six aggregates on the four nodes in the cluster. All aggregates are online. Node1 and Node3 form an HA pair
and Node2 and Node4 form an HA pair
cluster::> storage aggregate show
Aggregate Size Available Used% State #Vols Nodes RAID Status
--------- -------- --------- ----- ------- ------ ------ -----------
aggr_0 239.0GB 11.13GB 95% online 1 node1 raid_dp,
aggr_1 239.0GB 11.13GB 95% online 1 node1 raid_dp,
aggr_2 239.0GB 11.13GB 95% online 1 node2 raid_dp,
aggr_3 239.0GB 11.13GB 95% online 1 node2 raid_dp,
aggr_4 239.0GB 238.9GB 0% online 5 node3 raid_dp,
aggr_5 239.0GB 239.0GB 0% online 4 node4 raid_dp,
6 entries were displayed.
- Issue the command to start the aggregate relocation:storage aggregate relocation start -aggregate-list aggregate-1, aggregate-2... -node source-node -destination destination-node
The following command moves the aggregates aggr_1 and aggr_2 from Node1 to Node3. Node3 is Node1's HA partner. The aggregates can be moved only within the HA pair
cluster::> storage aggregate relocation start -aggregate-list aggr_1, aggr_2 -node node1 -destination node3
Run the storage aggregate relocation show command to check relocation status.
- Monitor the progress of the aggregate relocation with the storage aggregate relocation show command:storage aggregate relocation show -node source-node
The following command shows the progress of the aggregates that are being moved to Node3:
cluster::> storage aggregate relocation show -node node1
Source Aggregate Destination Relocation Status
------ ----------- ------------- ------------------------
aggr_1 node3 In progress, module: wafl
aggr_2 node3 Not attempted yet
2 entries were displayed.
When the relocation is complete, the output of this command shows each aggregate with a relocation status of Done.