25.17 Operating procedures after system switchover

When inheriting IP addresses, no action is required after system switchover, because the primary system and the secondary system have the same host name. When not inheriting IP addresses, you must perform the following procedures, because the primary system and the secondary system have different host names.

The following operations are also required when you use the standby-less system switchover (1:1) facility. Note that IP addresses are not inherited when the standby-less system switchover (effects distributed) facility is used. Because the switching destination differs for each server, the host name of the switching destination is used after system switchover; this is why the operations described below are required.

Organization of this section
(1) Operation commands and utilities
(2) Messages
(3) Acquisition of statistical information
(4) Client environment definition (applicable to the standby system switchover facility only)

(1) Operation commands and utilities

(a) Standby system switchover facility or standby-less system switchover (1:1) facility
(b) Standby system switchover facility or standby-less system switchover (1:1) facility

If system switchover occurs while a server is active, each server defined in the erroneous unit must be operated as a server belonging to the accepting unit. Because the switching destination differs for each server, servers cannot be operated grouped as a regular unit after system switchover occurs.

For this reason, you must specify the values shown in Table 25-52 when you issue operation commands.

Table 25-52 Specification values for operation commands when the standby-less system switchover (effects distributed) facility is used

Type of commandSpecification value
Before switchingAfter switching
Host name specification commandHost name of the regular unitHost name specification command
Unit identifier specification commandUnit identifier of the regular unitUnit identifier specification command
Server name specification commandOperation target server nameServer name specification command

In operations in which a host name or unit identifier is specified, the processing target differs before and after system switchover. Therefore, when the standby-less system switchover (effects distributed) facility is used, it is advisable to use operations that provide for server name specification.

When a host name is displayed in the processing results of an operation command, it is the host name of the accepting unit that is displayed.

Table 25-53 shows the standby-less system switchover (effects distributed) facility the execution targets when operation command options are specified. Be aware that the execution targets of the pdstart and pdstop commands are different from those shown in the table; for details about the pdstart and pdstop commands, see 25.13 Differences in the HiRDB operating procedures.

Table 25-53 Execution targets when operation command options are specified (for the standby-less system switchover (effects distributed) facility)

OptionConditionCommand operation mode*Command's execution target
-u-sUnit where system manager is definedTarget server
NoNo[Figure][Figure][Figure]System (or all running back-end servers in the system)
YesOffline[Figure]OfflineSpecified server that is a back-end server of the primary system in the regular unit
OnlineOfflineOfflineSpecified server that is a back-end server of the primary system in the regular unit
OnlineOnlineSpecified server that is a running back-end server of the running unit
YesNo[Figure][Figure][Figure]Specified unit (or all running back-end servers in the specified unit)
HostOffline[Figure]OfflineSpecified unit that is a host BES in the specified regular unit
OnlineOfflineOfflineSpecified unit that is a host BES in the specified regular unit
OnlineOnlineSpecified server that is a running BES in the running unit (-u specification is ignored)
GuestOffline[Figure]OfflineSpecified server that is a guest BES in the specified accepting unit
OnlineOfflineOfflineSpecified server that is a guest BES in the specified accepting unit
OnlineOnlineSpecified server that is a running back-end server in the running unit (-u specification is ignored)

Legend:

[Figure]: Not applicable

* Mode for determining the running system when entering a subcommand on a unit where the system manager is not defined.

(2) Messages

For the standby system switchover facility, the primary system's host name is displayed in messages.

For the standby-less system switchover (1:1) facility, the host name or unit identifier of the normal BES unit is displayed in messages for normal BES unit processing.

For the standby-less system switchover (effects distributed) facility, the host name of the accepting unit is displayed in messages.

(3) Acquisition of statistical information

For details about collecting statistical information after system switchover, see 25.13.6 (2) Process for collecting statistical information after a system switchover.

(4) Client environment definition (applicable to the standby system switchover facility only)

(a) HiRDB/Single Server

When only the host name of the primary system is specified in the PDHOST operand, you must perform the following procedure. This procedure is not necessary when the host names of the primary system and secondary system are both specified in the PDHOST operand.

Because the host name of the HiRDB to be connected is specified in the PDHOST operand, you must specify in the PDHOST operand after system switchover the host name of the running system. Therefore, after system switchover, the HiRDB administrator must notify all client users that the host name of HiRDB has changed. Client users must change the host name specified in the PDHOST operand to this new host name, then re-execute UAPs. Note that you will not be able to execute UAPs if you do not first change the host name specified in the PDHOST operand. For details about the PDHOST operand, see the manual HiRDB Version 8 UAP Development Guide.

(b) HiRDB/Parallel Server

When only the host name of the primary system is specified in the operands listed below, you must perform the following procedure. This procedure is not necessary when the host names of the primary system and secondary system are both specified in these operands.

Because the host name of the HiRDB to be connected is specified in one of these operands, the host name of the running system must be specified after system switchover in the applicable one of these operands. (the host name of the system manager is specified in the PDHOST operand and the host name of a front-end server is specified in the PDFESHOST operand). Therefore, after system switchover, the HiRDB administrator must notify all client users that the host name of HiRDB has changed. Client users must change the host name specified in the applicable operand to this new host name, then re-execute UAPs. Note that you will not be able to execute UAPs if you do not first change the host name specified in the applicable operand. For details about the PDHOST operand and the PDFESHOST operand, see the manual HiRDB Version 8 UAP Development Guide.

Remarks
  • The host name specified in the PDHOST operand needs to be changed only when system switchover occurs on the system manager unit.
  • The host name specified in the PDFESHOST operand needs to be changed when only system switchover occurs on a front-end server unit.
  • There is no need to change the PDHOST or PDFESHOST operand specification when system switchover occurs for a unit where no system manager or front-end server is defined.