Rejoining split aggregates or traditional volumes

Why you would rejoin split aggregates or traditional volumes

You might rejoin split aggregates or traditional volumes because you were forced to split them. This would be the case if you have configured a cluster in a MetroCluster configuration and a disaster breaks the cluster relationship.

Rejoining a split aggregate or traditional volume

When you rejoin a split traditional volume, Data ONTAP mirrors the data from one volume to the other and destroys data that existed on that volume before the rejoin. Likewise, when you rejoin a split aggregate, Data ONTAP mirrors the data from one aggregate to the other and destroys data that existed on that aggregate before the rejoining.

To rejoin a split aggregate or traditional volume, complete the following steps.

Step	Action
1	Determine the aggregate or traditional volume whose data you will keep and the aggregate or traditional volume whose data will be overwritten.
2	If the volume or aggregate whose data will be overwritten is online, take it offline by entering the following command for each volume or aggregate that was split: *{aggr \| vol} offline {aggrname* \| volname}** aggrname is the name of the aggregate. volname is the name of the traditional volume. Note An error message appears if the aggregate or volume is already offline.
3	Re-create the mirrored aggregate or traditional volume by entering the following command for each aggregate or traditional volume that was split: {aggr \| vol} mirror {aggrname1 \|volname1} -v {aggrname2 \|volname2} aggrname1 is the name of the aggregate whose data will be kept. volname1 is the name of the traditional volume whose data will be kept. aggrname2 is the name of the aggregate whose data will be overwritten by aggrname1. volname2 is the name of the traditional volume whose data will be overwritten by volname2.

Step

Action

Determine the aggregate or traditional volume whose data you will keep and the aggregate or traditional volume whose data will be overwritten.

If the volume or aggregate whose data will be overwritten is online, take it offline by entering the following command for each volume or aggregate that was split:

{aggr | vol} offline {aggrname | volname}

aggrname is the name of the aggregate. volname is the name of the traditional volume.

Note
An error message appears if the aggregate or volume is already offline.

Re-create the mirrored aggregate or traditional volume by entering the following command for each aggregate or traditional volume that was split:

{aggr | vol} mirror {aggrname1 |volname1} 

-v {aggrname2 |volname2}

aggrname1 is the name of the aggregate whose data will be kept.

volname1 is the name of the traditional volume whose data will be kept.

aggrname2 is the name of the aggregate whose data will be overwritten by aggrname1.

volname2 is the name of the traditional volume whose data will be overwritten by volname2.