Note that the following limitations apply to executing an operation command in conjunction with the standby system switchover facility (server mode):

• To execute an operation command during HiRDB termination processing, the HiRDBs on both systems must be engaged in termination processing (however, this requirement does not apply to the pdstart command).
• Normally, an operation command must not be executed by the HiRDB on the standby system. However, this restriction does not apply to the pdstart command, used for starting the HiRDB on the standby system, or to the following commands, which are executed when the HiRDB on the running system terminates abnormally and cannot be recovered:
  
  • Operation commands targeting a HiRDB files system on a shared disk
  • Operation commands targeting system log files, synchronization point dump files, or status files
  To execute an operation command in the HiRDB on the standby system, the following operations are required:
  
  • The HiRDB on both the running system and the standby system must be terminated. Execute the pdls -d ust command to make sure that both the HiRDB on the running system and the one on the standby system have terminated.
  • Before executing an operation command, use an OS command or a cluster software command to activate on the standby system the shared disk targeted by the operation command.
  • In a system switchover configuration that inherits IP addresses, before you execute an operation command, use an OS command or a cluster software command to activate on the standby system the IP address of the unit where you plan to execute the operation command.

If you change a HiRDB system definition or the HiRDB configuration when you are using a cluster software product other than HA Monitor, do not use a cluster software command to terminate HiRDB. Instead, use the pdstop command to normally terminate HiRDB only, and then change the HiRDB system definition or reconfigure HiRDB. When you have finished, you can use the pdstart command to start HiRDB only.

If HiRDB is stopped by the cluster software, it might not be possible to manipulate HiRDB files on the shared disk from either system. In this case, you must use an OS command to activate the shared disk.

You must be careful about executing the pdsetup -d command when HiRDB is forcibly or abnormally terminated. Do not enter Y at the command's prompt. If you do enter Y, it might become impossible to start HiRDB subsequently.

When Hitachi HA Toolkit Extension is used, the standby system unit will not wait for the running system unit to start. If a command is issued to the running system unit before the standby system unit has started, an error might occur and the standby system unit might abort (Phi1012). Therefore, wait for startup of the running system unit to finish before starting the standby system unit. If the standby system unit is started before startup of the running system unit has finished, the standby system unit might abort (Phi1012).

If a unit is placed in running server standby status^#1 when you try to start the unit, use the monact command of HA Monitor to start the unit as a running system^#2.

#1

Status in which *SBY* is displayed when HA Monitor's monshow command is executed.

#2

If a secondary system unit is started by the monact command as the running system unit, the messages listed below might be output repeatedly on the primary system unit until startup of the running system unit is completed. These messages cease to be output once startup of the running system unit is completed.

• KFPS05608-I
• KAMN305-E
• KAMN222-I

The KAMN305-E and KAMN222-I messages are output by HA Monitor.

If the time used by the OS differs significantly between the primary system machine and the standby system machine (that is, the time delay on the standby system machine is greater than the time required to perform a system switchover), note that HiRDB will be affected in the same way as when an incorrect operation is performed in an attempt to move the time back.

For details about how to change the time used by the OS, see 9.12 Changing the time used by the OS.