Re-creating mirrored aggregates to return a MetroCluster configuration to normal operation

To return the MetroCluster configuration to normal operation, you must re-create the mirrored aggregates.

Steps

Validate that you can access the remote storage by entering the following command:
aggr status -r
Note: A (level-0 resync in progress) message indicates that a plex cannot be rejoined.
Turn on the power to the node at the disaster site.
After the node at the disaster site boots up, it displays the following:
```
Waiting for giveback...(Press Ctrl-C to abort wait)
```
If the aggregates at the disaster site are online, take them offline by entering the following command for each aggregate that was split:
aggr offline disaster_aggr
disaster_aggr is the name of the aggregate at the disaster site.

Note: An error message appears if the aggregate is already offline.
Destroy every target plex that is in a level-0 resync state by entering the following command:
aggr destroy plex_name
Re-create the mirrored aggregates by entering the following command for each aggregate that was split:
aggr mirror aggr_name -v disaster_aggr
aggr_name is the aggregate on the surviving site’s node.

disaster_aggr is the aggregate on the disaster site’s node.

The aggr_name aggregate rejoins the disaster_aggr aggregate to reestablish the MetroCluster configuration.
Enter the following command at the partner node:
cf giveback
The node at the disaster site reboots.

Example of re-creating a mirrored aggregate

The following example shows the commands and status output when re-creating aggregates to reestablish the MetroCluster configuration.

The following output shows the aggregate status of the disaster site’s storage after reestablishing access to the partner at the surviving site:

filer1>aggr status -r
Aggregate mir1 (online, normal) (zoned checksums)
  Plex /mir1/plex0 (online, normal, active)
  RAID group /mir1/plex0/rg0 (normal)

RAID Disk Device HA  SHELF BAY CHAN  Used (MB/blks) Phys (MB/blks)
--------- ------ ------------- ----- -------------- -------------
parity   8a.3   8a   0     3   FC:B  34500/70656000 35003/71687368
data     8a.4   8a   0     4   FC:B  34500/70656000 35003/71687368
data     8a.6   8a   0     6   FC:B  34500/70656000 35003/71687368
data     8a.5   8a   0     5   FC:B  34500/70656000 35003/71687368

Aggregate mir1(1) (failed, partial) (zoned checksums)
  Plex /mir1(1)/plex0 (offline, failed, inactive)

  Plex /mir1(1)/plex6 (online, normal, resyncing)
    RAID group /mir1(1)/plex6/rg0 (level-0 resync in progress)

RAID Disk Device HA  SHELF BAY CHAN  Used (MB/blks) Phys (MB/blks)
--------- ------ ------------- ----- -------------- -------------
parity    6a.6   6a  0     6   FC:B  34500/70656000 35003/71687368 
data      6a.2   6a  0     2   FC:B  34500/70656000 35003/71687368 
data      6a.3   6a  0     3   FC:B  34500/70656000 35003/71687368 
data      6a.5   6a  0     5   FC:B  34500/70656000 35003/71687368

The mir1(1)/plex6 plex shows that a level-0 resynchronization was in progress; therefore, an attempt to rejoin the plexes fails, as shown in the following output:

filer1> aggr mirror mir1 -v mir1(1)
aggr mirror: Illegal mirror state for aggregate 'mir1(1)'

Because the mir1(1)/plex6 plex had a level-0 resynchronization in progress, the mir1(1) aggregate must be destroyed and the mir aggregate remirrored to reestablish a synchronous mirror, as shown in the following output:

filer1> aggr mirror mir1 -v mir1(1)
aggr mirror: Illegal mirror state for aggregate 'mir1(1)'
filer1> aggr destroy mir1(1)
Are you sure you want to destroy this aggregate? y
Aggregate 'mir1(1)' destroyed.
filer1> aggr mirror mir1
Creation of a mirror plex with 4 disks has been initiated. The disks need to be zeroed before addition to the aggregate. The process has been initiated and you will be notified via the system log as disks are added.