Skip to main content

storage failover takeover

Contributors
Suggest changes
PDFs

Take over the storage of a node's partner

Availability: This command is available to cluster administrators at the admin privilege level.

Description

The storage failover takeover command initiates a takeover of the partner node's storage.

Parameters

{ -ofnode {<nodename>|local} - Node to Takeover

This specifies the node that is taken over. It is shut down and its partner takes over its storage.

| -bynode {<nodename>|local} - Node Initiating Takeover }

This specifies the node that is to take over its partner's storage.

[-option <takeover option>] - Takeover Option

This optionally specifies the style of takeover operation. Possible values include the following:

  • normal - Specifies a normal takeover operation; that is, the partner is given the time to close its storage resources gracefully before the takeover operation proceeds. This is the default value.

  • immediate - Specifies an immediate takeover. In an immediate takeover, the takeover operation is initiated before the partner is given the time to close its storage resources gracefully. The use of this option results in an immediate takeover which does not do a clean shutdown. In case of NDU this can result in a NDU failure.

    Note If this option is specified, negotiated takeover optimization is bypassed even if the -bypass-optimization option is set to false.
Note If this option is specified, migration of data LIFs from the partner will be delayed even if the -skip-lif-migration-before-takeover option is not specified. If possible, migrate the data LIFs to another node prior to specifying this option.

  • allow-version-mismatch - If this value is specified, the takeover operation is initiated even if the partner is running a version of software that is incompatible with the version running on the node. In this case, the partner is given the time to close its storage resources gracefully before the takeover operation proceeds. However, the takeover operation will not be allowed if the partner has higher WAFL or RAID label versions. Use this value as part of a nondisruptive upgrade or downgrade procedure.

  • force - If this value is specified, the takeover operation is initiated even if the node detects an error that normally prevents a takeover operation from occurring. This value is available only at the advanced privilege level and higher.

    Note If this option is specified, negotiated takeover optimization is bypassed even if the -bypass-optimization option is set to false.
Note The use of this option can potentially result in data loss. If the HA interconnect is detached or inactive, or the contents of the failover partner's NVRAM cards are unsynchronized, takeover is normally disabled. Using the -force option enables a node to take over its partner's storage despite the unsynchronized NVRAM, which can contain client data that can be lost upon storage takeover.
[-bypass-optimization {true|false}] - Bypass Takeover Optimization (privilege: advanced)

If this is an operator-initiated planned takeover, this parameter specifies whether the takeover optimization is bypassed. This parameter defaults to false.

Note This parameter is ignored and negotiated takeover optimization automatically bypassed if the -immediate option, the -force option, or the -allow-disk-inventory-mismatch parameter is specified as part of the same storage failover takeover command.
[-allow-disk-inventory-mismatch {true|false}] - Disk inventory

If this parameter is specified, the takeover operation is initiated even if the local node cannot see the partner's filesystem disks.

Note If this parameter is specified, negotiated takeover optimization is bypassed even if the -bypass-optimization parameter is set to false.
Note The use of this parameter can potentially result in client outage.
[-skip-lif-migration-before-takeover <true>] - Skip Migrating LIFs Away from Node Prior to Takeover

This parameter specifies that LIF migration prior to takeover is skipped. However if LIFs on this node are configured for failover, those LIFs may still failover after the takeover has occurred. Without this parameter, the command attempts to synchronously migrate data and cluster management LIFs away from the node prior to its takeover. If the migration fails or times out, the takeover is aborted.

[-ignore-quorum-warnings <true>] - Skip Quorum Check Before Takeover

If this parameter is specified, quorum checks will be skipped prior to the takeover. The operation will continue even if there is a possible data outage due to a quorum issue.

[-override-vetoes <true>] - Override Vetoes

If this is an operator-initiated planned takeover, this parameter specifies whether the veto should be overriden. If this parameter is not specified, its value is set to false .

Note If this parameter is specified, negotiated takeover will override any vetos to continue with takeover.
Note The use of this parameter might result in the takeover proceeding even if the node detects issues that can potentially make the takeover dangerous or disruptive.
[-halt <true>] - Halt the Node That Is Taken Over

This parameter specifies whether the node being taken over should be halted. If the value is true, then the node being taken over is halted. If the value is false, then the node being taken over is shutdown and might be rebooted if AUTOBOOT is set to true. This parameter defaults to false.

[-check-only <true>] - Only Run Pre-Takeover Checks

This parameter initates a verification check of a possible future planned takeover. The check operation records any failures or issues that would prevent a takeover. Use the storage failover check-takeover command to view the result of the check. This parameter defaults to false.

Note This is a best effort operation. All checks passed does not guarantee a successful planned takeover as failures may occur during runtime.

Examples

The following example causes a node named node0 to initiate a negotiated optimized takeover of its partner's storage:

cluster1::> storage failover takeover -bynode node0

The following example causes a node named node0 to initiate an immediate takeover of its partner's storage:

cluster1::> storage failover takeover -bynode node0 -option immediate