4.1.0 HP PolyServe Software for Microsoft SQL Server administration guide (T5392-96074, October 2010)

Stop scripts must also handle recovery from events that may cause them to run
unsuccessfully.
For example, if the system encounters a problem, the script will fail and exit non-zero.
The service could then become active on another node, causing the Pre Stop script
to run on the original node even though the Post Start script did not complete
successfully.
Use custom scripts to modify Start/Stop activities
The monitor performs certain starting or stopping activities. If you need to take an
action before or after the starting or stopping activity, you can create a custom Start
or Stop script for the action and specify it on the Scripts tab for the monitor.
The default order for starting is:
• Run the monitor’s starting activities (if any)
• the custom Start script (if any)
If you want to reverse this order, preface the Start script with the prefix [pre] on
the Scripts tab.
The default order for stopping is:
• Run the custom Stop script (if any)
• Run the monitor’s stopping activities (if any)
If you want to reverse this order, preface the Stop script with the prefix [post] on
the Scripts tab.
Event severity
If a PostStart or PostStop script fails or times out, a monitor event is created on the
node where the failure or timeout occurred. An event is also created when a monitor
probe reports a status of DOWN. (Configuration errors can also cause these events.)
You can view the events on the PolyServe Management Console and clear them from
the Console after you have fixed the problems that caused them.
When an event is created, the ClusterPulse process may initiate failover of the
associated virtual host. You can configure the failover behavior with the Event Severity
attribute. There are two settings: CONSIDER and IGNORE.
CONSIDER. This is the default value. Events are considered when the ClusterPulse
process makes failover decisions.
IGNORE. Events are ignored; Post Start or Post Stop script failures and DOWN status
reports from the monitor will not cause failover. This is useful when the DOWN status
Configure Virtual SQL Servers84