storage aggregate resynchronization modify
Suggest changes
PDFs
Modify aggregate resynchronization priorities
Availability: This command is available to cluster administrators at the admin privilege level.
Description
The storage aggregate resynchronization modify command can be used to modify the resynchronization priority of an aggregate.
When the number of aggregates pending resynchronization is higher than the maximum number of concurrent resynchronization operations allowed on a node, the aggregates get resynchronized in the order of their "`resync-priority` " values.
For example, let the max-concurrent-resync under the storage aggregate resynchronization options directory for a node be set to two. If there are three aggregates waiting to be resynchronized, where their respective resync-priority values are high , medium , and low , then the third aggregate is not allowed to start resynchronization until one of the first two aggregates has completed resynchronizing.
Parameters
-aggregate <aggregate name>- Aggregate-
This parameter specifies the aggregate that is to be modified.
[-resync-priority {high(fixed)|high|medium|low}]- Resynchronization Priority-
This parameter specifies the new resynchronization priority value for the specified aggregate. This field cannot be modified for unmirrored or Data ONTAP system aggregates.
Possible values for this parameter are:
-
high: Mirrored data aggregates with this priority value start resynchronization first.
-
medium: Mirrored data aggregates with this priority value start resynchronization after all the system aggregates and data aggregates with 'high' priority value have started resynchronization.
-
low: Mirrored data aggregates with this priority value start resynchronization only after all the other aggregates have started resynchronization.
-
Examples
The following example changes the resync-priority of a specified aggregate to medium :
cluster1::> storage aggregate resynchronization modify -aggregate aggr1 -resync-priority medium