The storage aggregate resynchronization show command displays the relative resynchronization priority for each aggregate in the cluster. When a particular node restricts how many resync operations can be active concurrently, these priorities are used to prioritize the operations. The maximum concurrent resync operations for a node is displayed in the storage aggregate resynchronization options show command. If no parameters are specified, the command displays the following information about all the aggregates in the cluster:

Aggregate name
Node that owns the aggregate
Resync priority for the aggregate

Parameters

{ [-fields <fieldname>,…]

If you specify the -fields <fieldname>, … parameter, the command output also includes the specified field or fields. You can use '-fields ?' to display the fields to specify.

| [-instance ] }

If you specify the -instance parameter, the command displays detailed information about all fields.

[-aggregate <aggregate name>] - Aggregate

If this parameter is specified, the command displays the resynchronization priority only for the specified aggregate.

[-node {<nodename>|local}] - Node

If this parameter is specified, the command displays the resynchronization priority only for the aggregates owned by the specified node.

[-resync-priority {high(fixed)|high|medium|low}] - Resynchronization Priority

If this parameter is specified, the command displays only the resynchronization priority that matches the specified value. Possible values for this parameter are:

high(fixed): This value is reserved for Data ONTAP system aggregates, which cannot have any other value for this field. These aggregates always start their resynchronization operation at the first available opportunity. This value cannot be assigned to a data aggregate.
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.

When the number of aggregates waiting for resynchronization is higher than the maximum number of resynchronization operations allowed on a node, then the resync-priority field is used to determine which aggregate starts resynchronization first. This field is not set for unmirrored aggregates.

Examples

The following command displays the resynchronization priorities for all the aggregates in the cluster:

cluster1::> storage aggregate resynchronization show
Aggregate Node             Resync Priority
--------- ---------------- ---------------
aggr0_n1  cluster1-01      high(fixed)
aggr0_n2  cluster1-02      high(fixed)
aggr1     cluster1-01      low
aggr2     cluster1-01      high
aggr3     cluster1-01      medium
4 entries were displayed.

storage aggregate resynchronization options show

ONTAP 9.12.1 commands

storage aggregate resynchronization show

Description

Parameters

Examples

Related Links