3.4.3 MxDB for SQL Server Installation and Administration Guide

Chapter 3: Configuration and Operation 51

AUTORECOVER. If the Virtual SQL Server policy is AUTOFAILBACK,

when the probe fails, the ClusterPulse process automatically begins

failover of the associated Virtual SQL Server to a backup node. Failback

occurs in accordance with the policy setting for the Virtual SQL Server

(either

AUTOFAILBACK or NOFAILBACK). See “Configure Virtual SQL

Servers” on page 41 for a description of these settings.

NOAUTORECOVER. When the probe fails, the ClusterPulse process

automatically begins failover of the associated Virtual SQL Server to a

backup node. The monitor is then disabled on the original node. If the

Virtual SQL Server policy is

AUTOFAILBACK, you will need to manually

reenable the monitor before failback can occur. This option is useful when

integrating MxDB for SQL Server with a custom application, where

certain application-specific actions must be taken before the failback can

occur.

Service Priority: The service priority is used when the ClusterPulse

process fails over Virtual SQL Servers. Service priorities are natural

numbers, with 0 (zero) representing the highest priority and higher

numbers representing lower priorities. If multiple failures prevent

ClusterPulse from placing a Virtual SQL Server on a node where all of its

associated services are available, ClusterPulse next looks for a server

where the associated service with the highest priority is available. By

default, all service monitors have a priority of 0.

Probe Type: The probe type is set to single-probe for Virtual SQL Server

monitors. A single-probe monitor performs the probe function only on

the node where the monitor instance is active. The monitor instance is

activated on the node where the associated Virtual SQL Server is

activated, and the probe takes place on that node. The monitor instances

on other nodes are marked as “standby” on the Management Console.

If the Virtual SQL Server fails over to a backup node, the monitor instance

on the original node becomes inactive and the probe is no longer run on

that node. Matrix Server activates the Virtual SQL Server on the new

node, which causes the monitor instance on that node to change status

from “standby” to “active.” The monitor then begins probing on that

node and the Start script starts the application. If the monitor instance