Table 25-32 lists the methods of terminating HiRDB when using the standby system switchover facility.
Table 25-32 Terminating HiRDB when using the standby system switchover facility
Condition | Termination method | |
---|---|---|
Cluster software used is HA monitor | Terminating both the running system and the standby system | Use the pdstop command to terminate the running system HiRDB. The standby system HiRDB will terminate together with the running system. This situation also applies during planned termination or forced termination. To terminate at the unit level, use the pdstop -u command to terminate the running system unit. The standby system unit will terminate together with the running system unit. This situation also applies when the pdstop -z command is executed. |
Terminating only the standby system | Use the HA monitor monsbystp command to terminate only the standby system. | |
Cluster software other than HA monitor is used | Terminating both the running system and the standby system* | Use the pdstop command to terminate the running system HiRDB, then use the hatesbystp command in Hitachi HA Toolkit Extension to terminate HiRDB. Executing the pdstop command does not terminate the standby system HiRDB. This situation also applies to planned termination or forced termination. To terminate at the unit level, use the pdstop -u command to terminate the running system unit, then use the hatesbystp command in Hitachi HA Toolkit Extension to terminate the standby unit. Executing the pdstop -u command does not terminate the standby system unit. This situation also applies when the pdstop -z command is executed. |
Terminating only the standby system | Use the hatesbystp command in Hitachi HA Toolkit Extension to terminate the standby system HiRDB. |
Table 25-33 lists the methods of terminating HiRDB when you use the standby-less system switchover (1:1) facility.
Table 25-33 Terminating HiRDB when using the standby-less system switchover (1:1) facility
Objective | Command to execute | Remarks (effect on other unit or alternate portion) | |
---|---|---|---|
Terminating HiRDB | pdstop | No specific operation needs to be performed on the alternate BES. Operation does not change even when alternating units. | |
Terminating the normal BES unit | pdstop -u | Waiting status1 of the alternate portion is released. | |
Terminating the alternate BES unit | Normal operation | pdstop -u | Waiting status of the alternate portion in the alternate BES unit is released. |
Alternating | The alternate portion in the alternate BES unit also stops. Also, when the normal BES unit is in waiting status,2 the waiting status of the alternate BES unit is released. | ||
Terminating the alternate portion when alternating units | pdstop -u | Specify for the unit identifier the unit identifier of the normal BES unit. | |
Releasing waiting status of the alternate portion | hatesbystp3 | None | |
Releasing waiting status of the normal BES unit | hatesbystp4 |
Note: Termination at the server level is not possible.
1 The system is switched to the alternate BES unit only if the alternate portion is in waiting status. If the alternate portion is in waiting status, the system status is displayed as SBY in the execution results of the pdls -d ha command.
2 The system will be switched back to the normal BES unit only if the normal BES unit is in waiting status (that is, it will not be switched back to normal status from alternating status). If the normal BES unit is in waiting status, the system status is displayed as SBY in the execution results of the pdls -d ha command.
3 Use the monsbystp command of HA monitor or the hatesbystp command of Hitachi HA Toolkit Extension to release the waiting status of the alternate portion. Specify in the hatesbystp command the alias of the normal BES unit that corresponds to the alternate portion to be released from standby status.
4 Use the monsbystp command of HA monitor or the hatesbystp command of Hitachi HA Toolkit Extension to release the waiting status of the normal BES unit. Specify in the hatesbystp command the unit identifier of the normal BES unit that releases the waiting status.
Examples of terminating an alternate BES unit or normal BES unit are provided below.
This section explains how to terminate both the running system and the standby system.
Table 25-34 shows how the entire system is stopped when the standby-less system switchover (effects distributed) facility is used.
Table 25-34 Stopping the entire system when the standby-less system switchover (effects distributed) facility is used
Input location | Command | Option | Condition | Operation |
---|---|---|---|---|
-f | Forcibly/abnormally terminated server? | |||
Unit where system manager is defined | pdstop | No | Yes1 | Error (a new message, such as KFPS05063-E or its equivalent, is output) |
No | No2 | Stops the system. | ||
Yes | Yes | Stops the system forcibly (some units are already stopped). | ||
Yes | No | Stops the system forcibly. |
Table 25-35 shows the processing that occurs during system termination.
Table 25-35 Processing that occurs during system termination
Target | Processing detail |
---|---|
Unit | While the system is being stopped, the system manager stops all units (by executing pdstop -u UID (-f) or its equivalent). |
Server | When a unit is stopped while the system is being stopped, the system stops all host BESs and guest BESs at that unit (by executing pdstop -q -s server-name (-f) or its equivalent). |
When the system is stopped, the accepting status for guest BESs at an accepting unit is cancelled automatically regardless of whether the system is being terminated normally terminated or forcibly. This cancellation occurs even if a guest BES is active. For this reason, you need not take any action with regard to guest BESs.
Table 25-36 shows the processing that occurs for the various back-end servers during system termination when the standby-less system switchover (effects distributed) facility is used.
Table 25-36 Processing that occurs for the various back-end servers during system termination when the standby-less system switchover (effects distributed) facility is used
Back-end server's status | Processing | |
---|---|---|
Host BES | Running | Stops. |
Accepting status | Cancels the accepting status automatically. | |
Guest BES | Running | Stops automatically. |
Accepting status | Cancels the accepting status automatically. |
Figure 25-62 shows an example of system termination. In this example, the following servers are stopped when the system is stopped:
Additionally, the accepting status for the following servers is cancelled:
Figure 25-62 System termination example
Table 25-37 shows how a unit is stopped when the standby-less system switchover (effects distributed) facility is used.
Table 25-37 Stopping a unit when the standby-less system switchover (effects distributed) facility is used
Input location | Command | Option | Operation | ||
---|---|---|---|---|---|
-z | -u | -f | |||
Unit where system manager is defined | pdstop | No | Yes | No | Stops the target unit normally. |
Yes | Stops the target unit forcibly. | ||||
Target unit | pdstop | Yes | No | No | Stops the target unit forcibly. |
To stop a unit, stop all host BESs and guest BESs at the unit (by executing pdstop -q -s server-name (-f) or its equivalent).
Table 25-38 shows whether a unit can be stopped normally depending on the status of servers in the unit. When the standby-less system switchover (effects distributed) facility is used, a unit can be stopped normally regardless of whether any of its servers, host BESs or guest BESs, have stopped abnormally by themselves or have been stopped forcibly.
Table 25-38 Whether a unit can be stopped normally depending on the status of servers in the unit
Server status (both BESs and guest BESs) | Can the unit be stopped normally? | ||
---|---|---|---|
Starting/stopping1 | On standby2 | Stopped3 | Standby-less system switchover (effects distributed) facility |
No | No | No | Yes |
Yes | Yes | ||
Yes | No | Yes | |
Yes | Yes | ||
Yes | No | No | No |
Yes | No | ||
Yes | No | No | |
Yes | No |
Table 25-39 shows the processing for the various back-end servers during unit termination when the standby-less system switchover (effects distributed) facility is used.
Table 25-39 Processing that occurs for the various back-end servers during unit termination when the standby-less system switchover (effects distributed) facility is used
Running location | Back-end server state | Processing |
---|---|---|
Unit being stopped | Running | Stops. |
Accepting status | Cancels the accepting status. | |
Other unit | Running | No change. |
Accepting status | Cancels the accepting status automatically. |
Figure 25-63 Example of stopping a unit during normal operation
Figure 25-64 Example of stopping a unit that has accepted a guest BES
Figure 25-65 Example of stopping a unit that has only a guest BES
Table 25-40 shows how a server is stopped when the standby-less system switchover (effects distributed) facility is used.
Table 25-40 Stopping a server when the standby-less system switchover (effects distributed) facility is used
Input location | Command | Option | Operation | |||
---|---|---|---|---|---|---|
-z | -u | -s | -f | |||
Unit where system manager is defined | pdstop | No | No | Yes | No | Stops the target server2 |
Yes | Terminates forcibly the target servers in all active units in the HA group1. | |||||
Yes | Yes | No | Stops the target server2, 3. | |||
Yes | Stops the target server forcibly2. | |||||
Target unit | pdstop | Yes | No | Yes | No | Stops the target server (host BES) forcibly4. |
Table 25-41 Server termination results depending on the server status
Server status | Start result |
---|---|
Waiting for the running system to start | Cancels the wait for the running system to start. |
Accepting status | Cancels the accepting status. |
Active | Stops the server. |
Table 25-42 shows the processing for the various back-end servers during server termination when the standby-less system switchover (effects distributed) facility is used.
Table 25-42 Processing that occurs for the various back-end servers during server termination when the standby-less system switchover (effects distributed) facility is used
Running location | Back-end server status | Processing |
---|---|---|
Active unit | Operation target | Stops |
Other units | Accepting status | Cancels the accepting status. |
Figure 25-66 Example of stopping a host BES
Figure 25-67 Example of stopping a guest BES
This section explains how to stop only the standby system.
As when using the standby system switchover facility or standby-less system switchover (1:1) facility, the monsbystp command of HA monitor can be used to stop the standby system. When the standby-less system switchover (effects distributed) facility is used, you can also perform the operation from the unit where the system manager is defined.
Table 25-43 shows how to terminate the standby system when the standby-less system switchover (effects distributed) facility is used.
Table 25-43 Terminating the standby system when the standby-less system switchover (effects distributed) facility is used
Input location | Command | Operation target | Operation |
---|---|---|---|
Host where the operation-target server is located | monsbystp* | Back-end server in accepting status | Cancels the accepting status for a guest BES |
Unit where system manager is defined | pdstop -u -s |
Figure 25-68 shows an example of cancelling the accepting status for a guest BES.
Figure 25-68 Example of cancelling the accepting status for a guest BES
To cancel the accepting status for a guest BES, enter HA monitor's monsbystp command. When you use Hitachi HA Toolkit Extension, enter the hatesbystp command.
Figure 25-69 shows an example of stopping a host BES of the standby system.
Figure 25-69 Example of stopping a host BES of the standby system
To stop a host BES of the standby system, enter HA monitor's monsbystp command. When you use Hitachi HA Toolkit Extension, enter the hatesbystp command.