Moving a server while HiRDB is running

Move a HiRDB parallel server configuration front-end server (FES1) and back-end server (BES1). The following figure illustrates the procedure:

[Figure]

Use of the system reconfiguration command (pdchgconf command) eliminates the need to terminate HiRDB normally. Note that HiRDB Advanced High Availability must be installed in order to use this command.

Notes

You cannot move a system manager.
The disk on which you create the system files and the RDAREAs for the server to be moved must be shared by means of a SAN or other storage network system between both the current server machine and the new server machine.
You can move a server only if you are using the HP-UX or AIX editions of HiRDB. This is because OS commands must be used during the configuration change to disconnect and connect the shared disk, which means that servers can be moved only on operating systems that provide such commands (HP-UX and AIX).

Organization of this subsection: (1) Determine the memory requirements for unit 2; (2) Prepare shells for disconnecting and connecting the shared disk; (3) Create updated HiRDB system definitions; (4) Use the pdconfchk command to check the updated HiRDB system definitions; (5) Use the pdchgconf command to modify the HiRDB system definitions; (6) Modify client environment definitions

(1) Determine the memory requirements for unit 2

To move the servers, you must re-estimate the memory requirements for unit 2. You might also need to modify operating system parameters of the OS. For details about memory requirements and evaluating operating system parameters, see the HiRDB Version 9 Installation and Design Guide.

Note that you must restart the OS for changes to operating system parameters to take effect, which means that HiRDB must be terminated normally. In this example, we assume no operating system parameters are to be changed.

(2) Prepare shells for disconnecting and connecting the shared disk

Prepare the shells from which you will disconnect and connect the shared disk. Execute the shells as a superuser. For safety's sake, do not include in these shells any commands other than commands for disconnecting and connecting the disk.

Shell on current server machine: Create a shell ($PDDIR/conf/chgconf/diskdiscon.sh) containing the command for disconnecting the disk storing the system files and RDAREAs from the current server machine. The following shows an example on HP-UX:; /usr/sbin/vgchange -a n device-name

Shell on new server machine: Create a shell ($PDDIR/conf/chgconf/diskcon.sh) containing the command for connecting the disk storing the system files and RDAREAs onto the new server machine. The following shows an example on HP-UX:; /usr/sbin/vgchange -a y device-name

(3) Create updated HiRDB system definitions

Use the procedure explained below to create HiRDB system definitions that reflect the change in the server configuration.

Procedure

Create a $PDDIR/conf/chgconf directory.
Copy the current HiRDB system definition files into the directory that you created in step 1.
Modify the HiRDB system definitions that are in the $PDDIR/conf/chgconf directory.

(4) Use the pdconfchk command to check the updated HiRDB system definitions

 
pdconfchk -d chgconf

Check the HiRDB system definitions in the $PDDIR/conf/chgconf directory. If errors are detected, correct the HiRDB system definitions, and then execute the pdconfchk command again.

(5) Use the pdchgconf command to modify the HiRDB system definitions

 
pdchgconf

Replace the HiRDB system definitions with the updated HiRDB system definitions. At this time, the shells that you created in step (1) for disconnecting and connecting the disk are executed.

Note: If system reconfiguration processing fails, the pdchgconf command might end in an error without replacing the HiRDB system definitions. If the pdchgconf command ends in an error, check the connection state of the disks and the files in the $PDDIR/conf directory.

(6) Modify client environment definitions

Check if the following operands in the client environment definitions are specified; if the front-end server (FES1) that you moved is specified in these operands, change their values as appropriate:

PDFESHOST
PDSERVICEGRP
PDSERVICEPORT