25.14 Planned system switchover

This section explains the procedures for performing planned system switchover.

Organization of this section
(1) Standby system switchover facility
(2) Standby-less system switchover (1:1) facility
(3) Standby-less system switchover (effects distributed) facility

(1) Standby system switchover facility

To perform a planned system switchover:

Server mode
  1. Use the pdstop command to terminate the running system HiRDB (unit or server). Perform this step only when a product other than HA monitor is used in the cluster software.
    Also, if you specify the pdstop command in the termcommand operand of Hitachi HA Toolkit Extension, you do not have to execute the pdstop command at this time, because Hitachi HA Toolkit Extension executes it as an extension of the command in step 2.
  2. Use a cluster software command (monswap command in the case of HA monitor) to perform a planned system switchover. For details about planned system switchovers, see the documentation for the cluster software product.
  3. The HiRDB (or unit) that became the standby system must be placed in waiting status. Execute the pdstart command (pdstart -q command in the case of a HiRDB/Parallel Server) on the standby system HiRDB.
Monitor mode
  1. Use the pdstop command to terminate the running system HiRDB (or unit).
  2. Use a cluster software command (monswap command in the case of HA monitor) to perform a planned system switchover. For details about planned system switchovers, see the documentation for the cluster software product.
  • When the cluster software product used is HA monitor and you specify HiRDB termination in the shell you start with the termcommand operand in the server definition statement, you can perform a planned system switchover by simply executing the monswap command. For examples of shell creation, see 25.6.2(4) termcommand operand (applicable to the monitor mode only).
  • To perform a system switchover manually when the cluster software product used is ClusterPerfect, stop the running system then start the standby system. When system switchover occurs, the color of ClusterPerfect's ClusterPerfect system information window changes.

(2) Standby-less system switchover (1:1) facility

When performing a planned system switchover to the alternate BES unit, the alternate portion must be in waiting status. When switching the system back to the normal BES unit, the normal BES unit must be in waiting status. The procedure for performing a planned system switchover is explained below:

Procedure: Switching the system to the alternate BES unit
[Figure]
  1. Use the pdstop -z command to terminate the normal BES unit. Perform this step only when a product other than HA monitor is used in the cluster software.
    Also, when specifying the pdstop command in the termcommand operand of Hitachi HA Toolkit Extension, you do not have to execute the pdstop command at this point, because Hitachi HA Toolkit Extension executes the pdstop command as an extension of the command in step 2.
  2. Use a cluster software command (monswap command in the case of HA monitor) to perform a planned system switchover. For details about planned system switchovers, see the documentation for the cluster software product.

When you use the above procedure to perform a planned system switchover, the alternate BES unit performs normal BES unit processing. The normal BES unit becomes inactive. To switch the system back to the normal BES unit, use the following procedure to perform a planned system switchover again:

Procedure: Switching system back to the normal BES unit
[Figure]
  1. Use the pdstart -q command to place the normal BES unit in waiting status.
  2. Use a cluster software command (the monswap command in the case of HA Monitor) to perform a planned system switchover. The waiting status of the alternate portion is released.
  3. Use the pdstart -q command to place the alternate portion in waiting status.

(3) Standby-less system switchover (effects distributed) facility

For a planned system switchover, execute HA monitor's monswap command.

When this command executes, the back-end server at the switching-source unit is placed automatically on standby status.

If you are using Hitachi HA Toolkit Extension, enter the cluster software's planned system switchover command instead of the monswap command.

Table 25-48 shows the planned system switchover operation when you use the standby-less system switchover (effects distributed) facility.

Table 25-48 Planned system switchover operation when the standby-less system switchover (effects distributed) facility is used

Back-end server typeOperationMove destination
Host BESMoves to the switching destination with the highest priority; if there is no free space in the guest area, moves to the switching destination with the next highest priority.Guest BES
Guest BESHost BES
(a) Planned system switchover for a host BES

Figure 25-74 shows an example of planned system switchover for a host BES. In this example, a server machine (hostA) must be stopped for hardware maintenance of the host.

Figure 25-74 Example of planned system switchover for a host BES

[Figure]

In this example, planned system switchover is executed for the current BES on unt1. The procedure is as follows:

  1. In hostA, the monswap command is entered for BES1 and BES1 is switched to hostB.
  2. In hostA, the monswap command is entered for BES2 and BES2 is switched to hostC.

If you are using Hitachi HA Toolkit Extension, enter the cluster software's planned system switchover command.

(b) Planned system switchover for guest BESs (system reactivation)

Figure 25-75 shows an example of planned system switchover for guest BESs (system reactivation). In this example, a unit recovers from an error.

Figure 25-75 Example of planned system switchover for guest BESs (system reactivation)

[Figure]

In this example, BES5 and BES6, which had moved from unt3, are reactivated through planned system switchover. The procedure is as follows:

  1. In hostA, the monswap command is entered for BES5 and BES5 is switched to hostC.
  2. In hostB, the monswap command is entered for BES6 and BES6 is switched to hostC.

If you are using Hitachi HA Toolkit Extension, enter the cluster software's planned system switchover command.