You might rejoin split aggregates or traditional volumes because you were forced to split them. This would be the case if you have set up an active/active configuration in a MetroCluster configuration and a disaster breaks the active/active configuration.
Considerations
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.
Steps
- 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 volname1.
