Moving a server while HiRDB is stopped

Nonstop Database, HiRDB Version 9 System Operation Guide

11.6.2 Moving a server while HiRDB is stopped

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

[Figure]

Note: Because moving the system manager has far-ranging effects, we recommend that you do not move the system manager.

Organization of this subsection: (1) Determine the memory requirements for unit 2; (2) Use the pdrorg command to unload the table data on BES1, one RDAREA at a time; (3) Use the pdstop command to stop HiRDB normally; (4) Use the pdlogls command to check the status of the system log files in unit 1; (5) Use the pdlogunld command to unload any system log files in unload wait status; (6) Use the pdlogrm and pdstsrm commands to delete all system files from units 1 and 2; (7) Change the HiRDB system definition; (8) Use the pdloginit and pdstsinit commands to create the system files required for units 1 and 2; (9) Use the pdconfchk command to check the HiRDB system definitions; (10) Use the pdstart command to start HiRDB normally; (11) Use the pdcopy command to back up all RDAREAs; (12) Use the pdmod command to re-initialize the RDAREAs on BES1; (13) Use the pdrorg command to reload the table data in the unit that was moved, one RDAREA at a time; (14) Use the pdcopy command to back up all RDAREAs; (15) 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.

(2) Use the pdrorg command to unload the table data on BES1, one RDAREA at a time

For details about unloading table data on a per-RDAREA basis, see the manual HiRDB Version 9 Command Reference.

(3) Use the pdstop command to stop HiRDB normally

 
pdstop

Check that HiRDB terminates normally.

(4) Use the pdlogls command to check the status of the system log files in unit 1

 
pdlogls -d sys -s bes1
pdlogls -d sys -s bes2

(5) Use the pdlogunld command to unload any system log files in unload wait status

 
pdlogunld -d sys -s bes1 -g log01 -o /unld/unldlog01
pdlogunld -d sys -s bes2 -g log02 -o /unld/unldlog02

If you decide not to unload the system logs, use the pdcopy command to back up all RDAREAs. For details about making backups, see 6.4 Examples of backup.

(6) Use the pdlogrm and pdstsrm commands to delete all system files from units 1 and 2

 
pdlogrm -d sys -s fes1 -f /sysarea/log01           1
   :
pdlogrm -d spd -s fes1 -f /sysarea/sync01          2
   :
pdstsrm -s fes1 -f /sysarea/ssts01                 3
   :
pdstsrm -u UNT1 -f /sysarea/usts01                 4
   :

Explanation

Deletes the system log files for FES1, and BES1 to BES3.
Deletes the synchronization point dump files for FES1, and BES1 to BES3.
Deletes the server status files for FES1, and BES1 to BES3.
Deletes the unit status files for units 1 and 2.

(7) Change the HiRDB system definition

Create HiRDB system definitions that reflect the change in the server configuration.

(8) Use the pdloginit and pdstsinit commands to create the system files required for units 1 and 2

 
pdloginit -d sys -s fes1 -f /sysarea/log01 -n 5000          1
   :
pdloginit -d spd -s fes1 -f /sysarea/sync01 -n 5000         2
   :
pdstsinit -s fes1 -f /sysarea/ssts01 -c 3000                3
   :
pdstsinit -u UNT1 -f /sysarea/usts01 -c 3000                4
   :

Explanation

Creates system log files for FES1, and BES1 to BES3.
Creates synchronization point dump files for FES1, and BES1 to BES3.
Creates server status files for FES1, and BES1 to BES3.
Creates unit status files for units 1 and 2.

Because you re-created the status files, the error shutdown status of the RDAREAs is not inherited. If necessary, use the pdhold command to place RDAREAs in shutdown status again.

(9) Use the pdconfchk command to check the HiRDB system definitions

 
pdconfchk

If errors are detected, correct the HiRDB system definitions, and then execute the pdconfchk command again.

(10) Use the pdstart command to start HiRDB normally

 
pdstart

(11) Use the pdcopy command to back up all RDAREAs

For details about making backups, see 6.4 Examples of backup.

(12) Use the pdmod command to re-initialize the RDAREAs on BES1

For details about re-initializing RDAREAs, see 15.4 Modifying the size or attributes of an RDAREA (RDAREA reinitialization).

(13) Use the pdrorg command to reload the table data in the unit that was moved, one RDAREA at a time

Use the unload data file that you created in step (2) as input data. For details about reloading on a per-RDAREA basis, see the manual HiRDB Version 9 Command Reference.

(14) Use the pdcopy command to back up all RDAREAs

For details about making backups, see 6.4 Examples of backup.

(15) 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

We recommend that after the command has executed you check whether the execution results are correct. For details on how to check command execution results, see the manual HiRDB Version 9 Command Reference.