(a) servmax operand

You can specify this operand when the version of Hitachi HA Toolkit Extension is 01-04 or later.

For servers that are switched using Hitachi HA Toolkit Extension, specify 16 or 64 as the maximum number of servers that can be started concurrently as running servers or standby servers on a single server machine.

16: Sets 16 as the maximum number of servers that can be started concurrently.

64: Sets 64 as the maximum number of servers that can be started concurrently.

Specify 64 when the number of servers, which are the units for switching on a single server machine, exceeds 16.

The number of servers to be switched using Hitachi HA Toolkit Extension also includes products other than HiRDB that are to be switched. HiRDB computes the number of servers to be switched as follows:

• Total number of host BESs and guest BESs that are running on a single server machine and that are subject to effects-distributed standby-less system switchovers

(a) name operand

For the standby-less system switchover (effects distributed) facility, specify a HiRDB identifier and a server identifier, separated by a forward slash (/). Specify these items as follows if the HiRDB identifier is DB01 and the server identifier is BES1:

DB01/BES1

(b) switchtype operand

Use the switchtype operand to specify the processing to be performed when a server failure is detected.

switch:

When a unit terminates abnormally, a system switchover is performed and HiRDB restarts on the switchover destination system.

For the standby-less system switchover (effects distributed) facility, we recommend that you specify switch in the server definition file for the guest BES. When switch is specified, the guest BES switches to another unit if an error occurs in the unit in which the guest BES is running. As a result, the load on the unit can be distributed after it restarts.

restart:

The unit restarts in the system where the error occurred. Only if HiRDB cannot be restarted in the system where the error occurred, a system switchover occurs and HiRDB restarts on the switchover destination system (the system switchover is reported by output of the KFPS00715-E message).

For the standby-less system switchover (effects distributed) facility, we recommend that you not specify restart in the server definition file for the guest BES. If you specify restart, the guest BES continues processing if an error occurs in the unit in which the guest BES is running after the unit restarts. As a result, the load on the unit cannot be distributed after it restarts.

manual:

The systems are not switched automatically even if the unit cannot be restarted.

Therefore, do not specify manual in normal cases.

Hint

When you use the standby-less system switchover (effects distributed) facility, specify the same value in the switchtype operand of all servers in the HA group.

(c) termcommand operand

We recommend that you specify the pdstop -z -q command for several reasons. First, specifying the forced termination option is guaranteed to stop the unit. Second, during a planned system switchover, the standby system must inherit IP addresses when it restarts. Also, if a planned system switchover is performed when the running system unit has not started, the pdstop command specified in the termcommand operand will result in an error. If the termcommand operand is not specified, the pdstop command must be used to forcibly terminate the running system unit before a system switchover occurs. If a planned system switchover is performed while the running system unit is still active, there will be two running system units. If an error occurs, both systems might stop.

For the standby-less system switchover (effects distributed) facility, specify the pdstop -z -s command in the termcommand operand of all servers within the HA group.