What happens during giveback

The local node returns ownership of the aggregates and volumes to the partner node after you resolve any issues on the partner node or complete maintenance operations. In addition, the local node returns ownership when the partner node has booted up and giveback is initiated either manually or automatically.

The following process takes place in a normal giveback. In this discussion, Node A has taken over Node B. Any issues on Node B have been resolved and it is ready to resume serving data.

1. Any issues on Node B have been resolved and it displays the following message: Waiting for giveback
2. The giveback is initiated by the storage failover giveback command or by automatic giveback if the system is configured for it.

   This initiates the process of returning ownership of Node B's aggregates and volumes from Node A back to Node B.

3. Node A returns control of the root aggregate first.
4. Node B completes the process of booting up to its normal operating state.
5. As soon as Node B reaches the point in the boot process where it can accept the non-root aggregates, Node A returns ownership of the other aggregates, one at a time, until giveback is complete.

   You can monitor the progress of the giveback with the storage failover show-giveback command.

   Note: The storage failover show-giveback command does not (nor is it intended to) display information about all operations occurring during the storage failover giveback operation.

   You can use the storage failover show command to display additional details about the current failover status of the node, such as whether the node is fully functional, whether takeover is possible, and whether giveback is complete.

I/O resumes for each aggregate once giveback is complete for that aggregate; this reduces the overall outage window for each aggregate.