Understanding takeover and giveback
Takeover and giveback are the operations that let you take advantage of the HA configuration to perform nondisruptive operations and avoid service interruptions. Takeover is the process in which a node takes over the storage of its partner. Giveback is the process in which the storage is returned to the partner. You can initiate the processes in different ways.
When takeovers occur
Takeovers can be initiated manually or occur automatically when a failover event happens, depending on how you configure the HA pair . In some cases, takeovers occur automatically, regardless of configuration.
How hardware-assisted takeover speeds up takeover
Hardware-assisted takeover speeds up the takeover process by using a node's remote management device (SP or RLM) to detect failures and quickly initiate the takeover rather than waiting for Data ONTAP to recognize that the partner's heartbeat has stopped.
What happens during takeover
When a takeover occurs, the unimpaired partner node takes over the functions and disk drives of the failed node by creating an emulated storage system.
What happens during giveback
The local node returns ownership of the aggregates and volumes to the partner node after any issues on the partner node are resolved or maintenance is complete. In addition, the local node returns ownership when the partner node has booted up and giveback is initiated either manually or automatically.
Background disk firmware update and takeover and giveback
Background disk firmware updates affect HA pair takeover and giveback operations differently, depending on how those operations are initiated.