Stopping the VCS engine and related processes

The hastop command stops the High Availability Daemon (HAD) and related processes. You can customize the behavior of the hastop command by configuring the EngineShutdown attribute for the cluster.

The hastop command includes the following options:

    hastop -all [-force]
    hastop [-help]
    hastop -local [-force | -evacuate | -noautodisable]
    hastop -sys system ... [-force | -evacuate | -noautodisable]

Table: Options for the hastop command shows the options for the hastop command.

Table: Options for the hastop command

Option

Description

-all

Stops HAD on all systems in the cluster and takes all service groups offline.

-help

Displays command usage.

-local

Stops HAD on the system on which you typed the command

-force

Allows HAD to be stopped without taking service groups offline on the system. The value of the EngineShutdown attribute does not influence the behavior of the -force option.

-evacuate

When combined with -local or -sys, migrates the system's active service groups to another system in the cluster, before the system is stopped.

-noautodisable

Ensures that service groups that can run on the node where the hastop command was issued are not autodisabled. This option can be used with -evacuate but not with -force.

-sys

Stops HAD on the specified system.

More Information

About controlling the hastop behavior by using the EngineShutdown attribute