4.0.0 HP Polyserve Matrix Server Command Reference Guide (T5392-96048, March 2010)

[--restarts <number of restarts>]
The number of attempts that should be made to restart the MSDTC service instead
of immediately failing over the Virtual MSDTC Server. The default is one.
[--probeSeverity nofailover|autorecover|noautorecover]
This setting determines what happens when the MSDTC monitor probe fails. With
nofailover, when the monitor probe fails, the Virtual MSDTC does not fail over
to a backup node. With autorecover, the Virtual MSDTC fails over when the
monitor probe fails, and failback occurs according to the Virtual MSDTC policy
(either AUTOFAILBACK or NOFAILBACK). With noautorecover, failover occurs
to a backup node and the monitor is disabled on the original node.
[--ordering serial|parallel]
Whether Matrix Server enforces a strict ordering sequence when it runs Start or
Stop scripts. The default is serial, the strict ordering sequence.
[--recoveryScript <script>]
Runs after a monitor probe failure is detected, in an attempt to restore access to
the MSDTC 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.
[--startTimeout <seconds>]
The amount of time to wait for the Start script to complete.
[--stopScript <script>]
A script that runs on all other servers configured for the monitor to ensure that
the MSDTC service is not active on those servers.
[--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 a Virtual MSDTC. Service
priorities are natural numbers, with 0 (zero) representing the highest priority and
higher numbers representing lower priorities. If multiple failures prevent Matrix
Server from placing a Virtual MSDTC on a node where all of its associated ser-
mx commands132