(a) servmax operand

You can specify this operand when the version of HA Monitor is 01-08 or later.

For servers that are switched using HA Monitor, 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 HA Monitor 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 running system units and standby system units that are running on a single server machine and that are subject to standby system switchovers
• Total number of normal BES units and alternate BES units that are running on a single server machine and that are subject to standby-less system switchovers (1:1)
• Total number of host BESs and guest areas that are running on a single server machine and that are subject to standby-less system switchovers (effects distributed)

(b) multistandby operand

You can specify this operand when the version of HA Monitor is 01-08 or later.

This operand specifies whether to use the multi-standby function, which defines multiple standby systems for a single running system.

• use: Use the multi-standby function
• nouse: Do not use the multi-standby function

Specify use if the number of units belonging to the HA group is 3 or more. If you specify use, use the standbypri operand of the servers definition statement to specify priorities for the standby systems.

(a) acttype operand

To operate the system switchover facility in the server mode, specify server in this operand. To operate a system in the monitor mode, specify monitor in this operand.

(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.

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).

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.

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

(c) name operand

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

 
DB01/BES1

(d) alias operand

Specify an identifying name that is unique within the system to which HA Monitor is applied. You must specify the same identifying name in the primary and secondary systems.

For the standby-less system switchover (effects distributed) facility, we recommend that you specify the server identifier of the server subject to system switchovers.

(e) disk operand

Specify the name of the disk area (volume group and partition) in which a HiRDB file system area was created. For details, see the manual High-Availability System Monitoring Facility.

(f) lan_updown operand

For the standby-less system switchover (effects distributed) facility, activate the IP addresses specified in the -x option of the pdunit operand before starting the unit with the HA group name.

Do not specify an IP address specified in the -x option of the pdunit operand in the alias operand value's .up or .down file for HA Monitor.

(g) group operand

Specify this operand in order to perform grouped system switchovers. However, you do not need to specify this operand if the only server to be switched is HiRDB. Specify a server group name in this operand. The following examples provide guidelines for specifying server group names:

• If you are using OpenTP1 and performing grouped system switchovers, specify the same value as the definition file that set up the environment for the specified server in OpenTP1 of the same system.
• If you are using HiRDB Datareplicator and performing grouped system switchovers, specify the same value as the definition file that set up the environment for the specified server in HiRDB Datareplicator.

(h) initial operand

For the standby-less system switchover (effects distributed) facility, specify online for the normal BES unit and standby for the alternate BES unit.

(i) standbypri operand

You can specify this operand if the version of HA Monitor that you are using is 01-08 or later.

You can use this operand to specify priorities when you use the multi-standby function of HA Monitor (use must be specified in the multistandby operand in the sysdef definition file) to operate a system in a multi-standby configuration.

If you are using the standby-less system switchover (effects distributed) facility, specify priorities for guest BESs. For example, specify 1 for the guest BES with the first system switchover priority and 2 for the guest BES with the second priority.

(j) Specification example in the server definition file

For this example, the standby-less system switchover (effects distributed) facility is applied to the following 3-unit configuration:

Also, each of the following groups shares a global buffer:

• Group A: BES1A, BES2A, and BES3A
• Group B: BES1B, BES2B, and BES3B

The following table lists the priorities assigned to each unit.

Server	Online	Highest priority	Second priority
BES1A	unt1 [1]	unt2 [2]	unt3 [3]
BES1B	unt1 [4]	unt3 [5]	unt2 [6]
BES2A	unt2 [7]	unt3 [8]	unt1 [9]
BES2B	unt2 [10]	unt1 [11]	unt3 [12]
BES3A	unt3 [13]	unt2 [14]	unt1 [15]
BES3B	unt3 [16]	unt1 [17]	unt2 [18]

A specification example in the server definition file follows.

Server definition file for server machine 1

server name PDB1/bes1A, alias bes1A, patrol 10, disk /dev/vg01, initial online; ....[1] server name PDB1/bes1B, alias bes1B, patrol 10, disk /dev/vg02, initial online; ....[4] server name PDB1/bes2A, alias bes2A, patrol 10, disk /dev/vg03, initial standby, standbypri 2; ...[9] server name PDB1/bes2B, alias bes2B, patrol 10, disk /dev/vg04, initial standby, standbypri 1; ...[11] server name PDB1/bes3A, alias bes3A, patrol 10, disk /dev/vg05, initial standby, standbypri 2; ...[15] server name PDB1/bes3B, alias bes3B, patrol 10, disk /dev/vg06, initial standby, standbypri 1; ...[17]

Server definition file for server machine 2

server name PDB1/bes1A, alias bes1A, patrol 10, disk /dev/vg01, initial standby, standbypri 1; ....[2] server name PDB1/bes1B, alias bes1B, patrol 10, disk /dev/vg02, initial standby, standbypri 2; ...[6] server name PDB1/bes2A, alias bes2A, patrol 10, disk /dev/vg03, initial online; ...[7] server name PDB1/bes2B, alias bes2B, patrol 10, disk /dev/vg04, initial online; ...[10] server name PDB1/bes3A, alias bes3A, patrol 10, disk /dev/vg05, initial standby, standbypri 1; ...[14] server name PDB1/bes3B, alias bes3B, patrol 10, disk /dev/vg06, initial standby, standbypri 2; ...[18]

Server definition file for server machine 3

server name PDB1/bes1A, alias bes1A, patrol 10, disk /dev/vg01, initial standby, standbypri 2; ...[3] server name PDB1/bes1B, alias bes1B, patrol 10, disk /dev/vg02, initial standby, standbypri 1; ...[5] server name PDB1/bes2A, alias bes2A, patrol 10, disk /dev/vg03, initial standby, standbypri 1; ...[8] server name PDB1/bes2B, alias bes2B, patrol 10, disk /dev/vg04, initial standby, standbypri 2; ...[12] server name PDB1/bes3A, alias bes3A, patrol 10, disk /dev/vg05, initial online; ...[13] server name PDB1/bes3B, alias bes3B, patrol 10, disk /dev/vg06, initial online; ...[16]