What happens during healing (MetroCluster IP configurations)
During healing in MetroCluster IP configurations, the resynchronization of mirrored aggregates occurs in a phased process that prepares the nodes at the repaired disaster site for switchback. It is a planned event, thereby giving you full control of each step to minimize downtime. Healing is a two-step process that occurs on the storage and controller components.
Differences with MetroCluster FC configurations
In MetroCluster IP configurations, you must boot the nodes in the disaster site cluster before the healing operation is performed.
The nodes in the disaster site cluster must be running so that the remote iSCSI disks can be accessed when aggregates are resynchronized.
If the disaster site nodes are not running, the healing operation fails because the disaster node cannot perform the disk ownership changes needed.
Data aggregate healing
After the problem at the disaster site is resolved, you start the storage healing phase:
Checks that all nodes are up and running at the surviving site.
Changes ownership of all the pool 0 disks at the disaster site, including root aggregates.
During this phase of healing, the RAID subsystem resynchronizes mirrored aggregates, and the WAFL subsystem replays the nvsave files of mirrored aggregates that had a failed pool 1 plex at the time of switchover.
If some source storage components failed, the command reports the errors at applicable levels: Storage, Sanown, or RAID.
If no errors are reported, the aggregates are successfully resynchronized. This process can sometimes take hours to complete.
Root aggregate healing
After the aggregates are synchronized, you perform the root aggregate healing phase. In MetroCluster IP configurations, this phase confirms that aggregates have been healed.