8.4.2 Locked server environment settings (servers_opt)
This subsection explains the format of the locked server environment definition file and how to define the file.
- Organization of this subsection
(1) Format of definition
The following shows the format of a definition:
Δ0exclusive_serversΔ0:Δ0server-alias-nameΔ0:Δ0server-alias-nameΔ0↓
- Legend:
-
Δ0: Zero or more spaces or tabs
↓: End-of-line code
- Important
-
-
A hash mark (#) at the beginning of a line indicates that the codes from the hash mark through the end-of-line code constitute a comment.
-
Specify one operand per line. The maximum length of a line is 2,048 characters.
-
The definition is checked when HA Monitor is started, when a server is started, and when the definition check command (moncheck command) is executed. If a definition error is detected, the startup processing is terminated.
-
If this definition file contains only comments or this definition file is missing, no definition error results.
-
(2) Definition procedure
You create the file that defines the locked server environment under the file name servers_opt in the directory for HA Monitor environment settings.
We recommend that you create the locked server environment definition file on a host that contains only standby servers.
The following shows a locked server environment definition file:
# Locked server environment definition : server alias : server alias exclusive_servers :server-alias-name :server-alias-name[:server-alias-name...]
The following explains the operands used to define locked servers.
(a) exclusive_servers
User-specified values
|
Value type |
Range of numerical values |
Can be omitted |
Assumed value when this value is omitted |
|---|---|---|---|
|
-- |
-- (Units: --) |
Yes |
-- |
Description
Specifies all the servers that are to be locked, expressed by the server alias names specified in the alias operand in the server environment definition.
To lock servers on a server group basis, specify the server alias names of all servers that belong to all groups to be locked.
If one of the specified servers becomes the active server, all the remaining specified servers that satisfy the following conditions are terminated:
-
The server is starting as a standby server, is on standby, is waiting for restart of the active server, is waiting for the active server to be started, is waiting for hot standby processing, or is waiting for grouped-system switchover.
-
The server is not defined in the group operand in the server environment definition under the same group name as the server that will become the active server.
The maximum number of server alias names that can be specified depends on the maximum number of servers that can be run on one host. The maximum number of server alias names that can be specified is shown below for each maximum number of servers that can be run per host. Note that the number of specifiable server alias names includes the resource server.
-
2 to 24 alias names when the maximum number of servers is 16
-
2 to 96 alias names when the maximum number of servers is 64
-
2 to 192 alias names when the maximum number of servers is 128 or more
You can specify more than one exclusive_servers operand.
If a server with a specified server alias name is already running as the active server, the other servers that are also specified can no longer be started. To start any of those servers, take either of the following actions:
-
Terminate the active server and then start the desired server.
-
Switch over the active server to the remote host by performing planned hot standby processing and then start the desired server.