SFHA Solutions 6.0.1 – Using the hastop command to stop the VCS engine and related processes
Use the hastop command to stop the Veritas Cluster Server (VCS) engine (High Availability Daemon, HAD) and related processes on all the nodes, on a local node, or on a specific node of the cluster. You can customize the behavior of the hastop command by configuring the EngineShutdown attribute for the cluster. The value of the EngineShutdown attribute, a cluster attribute, specifies how the engine is to proceed when you issue the hastop command.
The hastop command is available after the VRTSvcs package is installed on a cluster node.
The following links provide more information on using the hastop command:
- Stopping the VCS engine and related processes
- About controlling the hastop behavior by using the EngineShutdown attribute
- Additional considerations for stopping VCS
- Veritas Cluster Server command line reference
You can use the hastop command with the following user-defined service group attributes:
- Evacuate attribute – allows you to issue hastop -local –evacuate to VCS to automatically fail over a service group to another node on the cluster.
- SysDownPolicy attribute – determines whether a service group is autodisabled when the system is down and if the service group is taken offline when the system is rebooted or is shut down gracefully.
For more information on the Evacuate and SysDownPolicy attributes, see:
For more information on using the hastop command to stop the VCS engine and related processes, see:
hastop (1M) manual pages:
Veritas Cluster Server documentation for other releases and platforms can be found on the SORT website.