(a) Information needed in the primary and secondary systems

It is essential to check that the following information is the same in both systems (primary system and secondary system):

• Versions of HiRDB and related programs
• HiRDB administrator's environment (user ID, group ID, and environment variables)
• Absolute path names of the HiRDB directories
• HiRDB system definitions
• HiRDB file definition formats
• Users' execute-form programs

(b) Notes on environment setup

• Set up the HiRDB environment in both the primary system and the secondary system. Use the same version of HiRDB in the primary system and the secondary system. Also, when upgrading HiRDB, be sure to upgrade both the primary system and the secondary system.
• Do not create the HiRDB directory on a shared disk.
• When a DNS server is not used, register a re-allocatable IP address in the hosts file.
• To operate a HiRDB/Parallel Server in the server mode, install the following products and set up the environment:
• Hitachi HA Toolkit Extension (for the primary and secondary system machines) (not necessary when the cluster software used is HA monitor)
• The system switchover facility is not applicable to a recovery-unnecessary front-end server unit.

Notes on using ClusterPerfect

Use the following command to stop the ClusterPerfect daemon before setting up the HiRDB environment; to execute this command, you must have root privileges:

# /etc/rc.d/init.d/dncware_daemon stop

Execute the following command to start the ClusterPerfect daemon:

# /etc/rc.d/init.d/dncware_daemon start

• Install and set up the environment for the following products:
  
  • HiRDB Advanced High Availability (for all server machines)
  • Hitachi HA Toolkit Extension (for normal BES and alternate BES units) (not necessary when the cluster software used is HA monitor)
• Define only back-end servers on the normal BES units and alternate BES units. The standby-less system switchover (1:1) facility cannot be used on units that include servers other than back-end servers.
• There is no need to provide a HiRDB directory for an alternate BES.
  Because the standby-less system switchover (1:1) facility uses the HiRDB directory of an alternate BES unit, there is no need to provide HiRDB directories specifically for the alternate BESs. That is, the pdsetup command is not necessary for an alternate BES.
  
• Allocate system definition files.
  In each unit comprising the group, allocate a back-end server definition file to each back-end server. The parameters to be set in the unit control information definition as the default values for back-end server definition must be defined in the system common definition or a back-end server definition file.
  

• Install and set up the environment for the following products:
  
  • HiRDB Advanced High Availability (for all server machines)
  • Hitachi HA Toolkit Extension (for the regular units and accepting units) (not necessary when the cluster software used is HA monitor)
• Define only back-end servers on regular units and accepting units. Units that include servers other than back-end servers cannot be used with the standby-less system switchover (effects distributed) facility.
• There is no need to provide a HiRDB directory for a guest BES.
  Because the standby-less system switchover (effects distributed) facility uses the HiRDB directory of an accepting unit, there is no need to provide HiRDB directories specifically for the guest BESs. That is, the pdsetup command is not necessary for a guest BES.
  
• Allocate system definition files.
  In each unit comprising the HA group, allocate a back-end server definition file to each back-end server. The parameters to be set in the unit control information definition as the default values for back-end server definitions must be defined in the system common definition or a back-end server definition file.