You can control when automatic takeovers occur by setting the appropriate options.
Reasons for automatic takeover
You can set options to control whether automatic takeovers occur due to different system errors. In some cases, automatic takeover occurs by default unless you disable the option, and in some cases automatic takeover cannot be prevented.
Commands for performing a manual takeover
You need to know the commands you can use when initiating a takeover. You can initiate a takeover on a node in an HA pair to perform maintenance on that node while still serving the data on its disks, array LUNs, or both to users.
Enabling and disabling takeover
You might want to use the cf disable command to disable takeover if you are doing maintenance that typically causes a takeover. You can reenable takeover with the cf enable command after you finish maintenance.
Enabling and disabling takeover on reboot
The takeover on reboot option enables you to control whether an automatic takeover occurs when a node reboots. This automatic takeover, and the automatic giveback that follows after the reboot is complete, can reduce the outage during which the storage belonging to the rebooting system is unavailable.
Enabling and disabling automatic takeover of a panicked partner Data ONTAP is configured by default to initiate a takeover immediately if the partner node panics. This shortens the time between the initial failure and the time that service is fully restored because the takeover can be quicker than the recovery from the panic, although the subsequent giveback causes another brief outage.
Takeover of vFiler units and the vFiler limit
The vFiler limit, set with the vfiler limit command, determines how many vFiler units can exist on a system. In an HA pair, if the two systems have different vFiler limits, some vFiler units might not be taken over if a takeover occurs.