3.4.3 MxDB for SQL Server Installation and Administration Guide

Chapter 3: Configuration and Operation 54

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 an SQL 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 File Server. 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 or the action performed by the scripts is

not critical, but is important enough that you want to keep a record of it.

Script Ordering

Script ordering determines the order in which the Post Start and Post Stop

scripts are run when a Virtual SQL Server moves from one node to

another. If you do not configure the SQL monitor with Post Start and Post

Stop scripts, the script ordering configuration has no effect. There are two

settings:

SERIAL and PARALLEL.

SERIAL. This is the default setting. When a Virtual SQL Server moves

from one node to another, The following strict ordering sequence for

running Post Start and Post Stop scripts is enforced:

1. The Post Stop script is run on all nodes where the virtual server

should be inactive.

2. ClusterPulse waits for all Post Stop scripts to complete.

3. The Post Start script on the node where the virtual server is becoming

active.