3.6.0 Matrix Server Command Reference (5697-7083, December 2007)

Chapter 3: mx Commands 123

[--recoveryScript <script>]

Runs after a monitor probe failure is detected, in an attempt to restore the

SQL service.

[--recoveryTimeout <seconds>]

The amount of time to wait for the script to complete.

[--startScript <script>]

When Matrix Server selects the active server for the SQL service, the Start

script runs on that server.

[--stopScript <script>]

A script that runs on all other servers configured for the monitor to ensure

that the SQL service is not active on those servers.

[--startTimeout <seconds>]

The amount of time to wait for the Start script to complete.

[--stopTimeout <seconds>]

The amount of time to wait for the Stop script to complete.

[--eventSeverity consider|ignore]

Whether Matrix Server takes service monitor events (such as a failure or

timeout of a Start or Stop script) into consideration when it makes failover

decisions. The default is consider.

[--priority <priority>]

The service priority is used when Matrix Server 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 preventMatrix Server from placing a Virtual SQL Server on a node

where all of its associated services are available, Matrix Server next looks for a

server where the associated service with the highest priority is available. The

default is 0.

[--revirtualize yes|no]

Whether existing data files should be used for this Virtual SQL Instance.

clear—Clear a monitor event

mx vsqlinstance clear <vsql\instance> <netif> ...

delete—Delete a Virtual SQL Instance

mx vsqlinstance delete <vsql\instance>