The storage failover giveback command returns storage that has failed over to a node’s partner back to the home node. This operation fails if other resource-intensive operations (for instance, system dumps) are running and make the giveback operation potentially dangerous or disruptive. Some options are available only at the advanced privilege level and higher. Run the storage failover show-giveback command to check the status of giveback operations.

NOTE:

If the system ID of the partner has changed while the node is in takeover mode, the storage failover giveback command updates the ownership of the partner’s disks to the new system ID while giving back.
If the giveback operation fails due to the operation being vetoed by a subsystem, check the syslog or EMS output for a subsystem-specific reason for the abort. The corrective action is subsystem-specific and is detailed in the corrective action portion of the message. Follow the corrective action specified by the subsystem and then reissue the storage failover giveback command. If you cannot perform the corrective action, then use the override-vetoes option in the storage failover giveback command to force the giveback.
If the giveback operation fails because the node cannot communicate with its partner, check the EMS output for the corrective action. Follow the corrective action and then reissue the storage failover giveback command. If you cannot perform the corrective action, then use the -require-partner-waiting false option in the storage failover giveback command to force the giveback. This parameter is available only at the advanced privilege level and higher.
If the node does not receive notification that the partner has brought online the given-back aggregate and its volumes, the storage failover show-giveback command displays the giveback status for the aggregate as failed. A possible reason for this failure is that the partner is overloaded and slow in bringing the aggregate online. Run the storage aggregate show command to verify that the aggregate and its volumes are online on the partner node. The node will not attempt the giveback operation for remaining aggregates. To force the giveback, use the -require-partner-waiting false option in the storage failover giveback command. This parameter is available only at the advanced privilege level and higher.

Parameters

{ -ofnode {<nodename>|local} - Node to which Control is Givenback: Specifies the node whose storage is currently taken over by its partner and will be given back by the giveback operation.
| -fromnode {<nodename>|local} - Node Initiating Giveback }: Specifies the node that currently holds the storage that is to be returned to the partner node.
[-require-partner-waiting {true|false}] - Require Partner in Waiting: If this optional parameter is used and set to false, the storage is given back regardless of whether the partner node is available to take back the storage or not. If this parameter is used and set to true, the storage will not be given back if the partner node is not available to take back the storage. If this parameter is not used, the behavior defaults to the setting of the -check-partner option set with the storage failover modify command.
[-override-vetoes <true>] - Override All Vetoes: If this optional parameter is used, the system overrides veto votes during a giveback operation. If this parameter is not used, the system does not proceed with a giveback if it is vetoed. This parameter, if used, can only be set to true.
[-only-cfo-aggregates <true>] - Giveback Only CFO Aggregates: If this optional parameter is used, giveback of only the CFO aggregates (root aggregate and CFO style data aggregates) will be attempted. If this parameter is not used, giveback of all the aggregates (CFO and SFO aggregates) will be attempted. This parameter, if used, can only be set to true.

Examples

The following example gives back storage that is currently held by a node named node1. The partner must be available for the giveback operation to occur.

node::> storage failover giveback -fromnode node1

The following example gives back only the CFO aggregates to a node named node2 (the aggregates are currently held by a node named node1). The partner must be available for the giveback operation to occur, and the veto-giveback process can be overridden.

node::> storage failover giveback -ofnode node2
-override-vetoes true -only-cfo-aggregates true

ONTAP 9.13.1 commands

storage failover giveback

Description

Parameters

Examples

Related Links