Managing takeover

You manage takeover by performing either of the following tasks:

Enabling and disabling takeover for the cluster, as described in the next section, "Enabling and disabling takeover."
Initiating a takeover of the partner by the local filer, as described in "Initiating a takeover."

You might want to disable takeover if you are doing maintenance work that normally causes a takeover, then reenable takeover when you have finished.

You can issue this command from either filer in the cluster.

To halt a filer and prevent its partner from taking over, enter the following command:

halt -f

This is useful if you need to perform maintenance on both the filer and its disks.

You might want to initiate a takeover to do maintenance work on a filer in the cluster while still serving the data on the disks of that filer.

You can initiate a takeover in the two ways described in the following table.


Method	Description
`cf takeover`	Initiates a takeover of the partner of the local filer. Takeover is aborted if time-consuming operations, such as a dump, are in progress.
cf takeover -f	Initiates a takeover of the partner of the local filer regardless of whether time-consuming operations, such as a dump, are in progress.
`cf forcetakeover`	Tells the cluster monitor to ignore some configuration problems that otherwise prevent a takeover, such as unsynchronized NVRAM due to a faulty interconnect connection. It then initiates a takeover of the partner of the local filer. Caution: Use `cf forcetakeover` only in certain controlled circumstances, when you cannot get `cf takeover` to succeed. You can lose uncommitted data with this command.

Part No. 210-02334
File: clust9.htm
Last updated: 04/26/99 08:11:41