To acquire a backup while HiRDB is running, use the following procedure to acquire the information on the first unload log file to be specified.

Procedure

1. Execute the pdlogswap -d sys -w command to swap the system log files and collect a synchronization point dump. In the case of a HiRDB parallel server configuration, swap the system log files of all backup acquisition target servers.
2. Execute the pdlogls -d sys and pdlogatul -d sys -i commands, and from the execution results, record the following types of information for the current system log file:
   Server name
   File group name
   Server run ID
   Generation number
   The system log file confirmed here becomes the first unload log file to be specified.
   
3. Use the database copy utility (pdcopy) or the backup facility of another product to acquire a backup.
   

   Reference note

   If you specify the -z and -p options when executing the pdcopy command in step 3, the system log file information necessary for database recovery is output to the processing result list of the pdcopy command. Since the information acquired during the execution of the pdcopy command is more accurate than the information obtained earlier using the pdlogls -d sys and pdlogatul -d sys -i commands, we recommend that you specify the -z and -p options when executing the pdcopy command if possible.

If you are acquiring a backup while HiRDB is stopped, or in a case in which HiRDB was started using the pdstart -r command, use the following procedure to acquire the information on the first unload log file to be specified.

Procedure

1. Use the database copy utility (pdcopy) or the backup facility of another product to acquire a backup.
2. Normally terminate HiRDB (if HiRDB was started using the pdstart -r command, normally terminate it first, and then normally start it).
3. Immediately following normal startup of HiRDB, execute the pdlogls -d sys and pdlogatul -d sys -i commands, and from the execution results, record the following types of information for the current system log file:
   Server name
   File group name
   Server run ID
   Generation number
   The system log file confirmed here becomes the first unload log file to be specified.
   

In this example, a backup of the back-end server (bes1) is acquired while HiRDB is running and while the automatic log unloading facility is being used.

1. Execute the pdlogswap -d sys -w command to swap the system log files and collect a synchronization point dump.
   

   pdlogswap -d sys -s bes1 -w

   If the return value of the pdlogswap command is 4, the synchronization point dump is not enabled, and therefore message KFPS02183-I is issued. You must wait for a synchronization point dump to be enabled.
   
2. Execute the pdlogls -d sys and pdlogatul -d sys -i commands.
   

   pdlogls -d sys -s bes1 HOSTNAME : dbhost1(153027) Group Type Server Gen No. Status Run ID Block No. Ex-Status logfg01 sys bes1 13 os----u 3a765d6d eff fc8 -------- logfg02 sys bes1 14 os----u 3a765d6d fc9 1092 -------- logfg03 sys bes1 15 os----u 3a765d6d 1093 115b -------- logfg04 sys bes1 16 osu---u 3a765d6d 115c 1226 -------- logfg05 sys bes1 17 oc-d--u 3a765d6d 1227 1227 -------- logfg06 sys bes1 12 os----u 3a765d6d e35 efe --------

   pdlogatul -d sys -s bes1 -i HOSTNAME : dbhost1(153153) SERVER_NAME:bes1 AUTO_LOG_UNLOAD NOW_UNLOAD_LOG_GROUP CREATE_DIR ACTIVE **** /unload_dir CURRENT LOG GENERATION INFO. LOG_GROUP GEN_NO. SERVER_RUN_ID RUN_ID UNLOAD_FILE_NAME logfg05 17 3a765d82 3a765d6d bes1_3a765d820017_logfg05

   From the above results, record the following types of information for the current system log file (the underlined areas):
   
   • Server name: bes1
   • File group name: logfg05
   • Server run ID: 3a765d82
   • Generation number: 17
   What must be checked here is the server run ID (SERVER_RUN_ID). Do not confuse it with the run ID (RUN_ID).
   
3. Use the database copy utility (pdcopy) to acquire a backup.
   

   pdcopy -m /rdarea/mast_rdarea/mast_rdarea01 -M r -s bes1 -b /pdcopy/backup/bes1bkup01 -z /pdcopy/logpoint/bes1logp01 -p /pdcopy/result/bes1result01

   Explanation

   -m: Specifies the name of the first HiRDB file in the master directory RDAREA.

   -M: Specifies the reference-possible mode for the backup acquisition mode.

   -s: Specifies that all RDAREAs on back-end server bes1 are to be backed up.

   -b: Specifies the name of the backup file.

   -z: Specifies the name of the log point information file.

   -p: Specifies the file name for the processing result list for the pdcopy command.

Reference note

To identify the first unload log file to be specified from the processing result list of the pdcopy command, record the <<LOG FILE INFORMATION>> information. An output example follows. The underlined areas indicate the information to be recorded.

*** DB BACKUP INFORMATION LIST *** BACKUPMODE : EXCLUSIVE <<LOG FILE INFORMATION>> SYSTEM ID : HRD1 UNIT ID : UNT1 TYPE : sys SERVER NAME : bes1 SERVER RUN ID : 3a765d82 LOG SERVER RUN ID : 3a765d6d FILE NAME : logfg05 GENERATION NO : 17 BLOCK NO : 1227 HEADER WRITE COUNTER : 3 HEADER WRITE TIME : 3a765d7a

• Server name: bes1
• File group name: logfg05
• Server run ID: 3a765d82
• Generation number: 17

In this example, a backup of the dictionary server (dic) is acquired when HiRDB was started using the pdstart -r command and when the automatic log unloading facility is used.

1. Use the database copy utility (pdcopy) to acquire a backup.
   

   pdcopy -m /rdarea/mast_rdarea/mast_rdarea01 -M x -s dic -b /pdcopy/backup/dicbkup01

   Explanation

   -m: Specifies the name of the first HiRDB file in the master directory RDAREA.

   -M: Specifies the reference/update-impossible mode for the backup acquisition mode.

   -s: Specifies that all RDAREAs on back-end server dic are to be backed up.

   -b: Specifies the name of the backup file.

2. Normally terminate HiRDB, and then normally start it.
   

   pdstop pdstart

3. Immediately following normal startup of HiRDB, execute the pdlogls -d sys and pdlogatul -d sys -i commands.
   

   pdlogls -d sys -s dic HOSTNAME : dbhost1(152953) Group Type Server Gen No. Status Run ID Block No. Ex-Status logfg01 sys dic 1 oc-d--u 3a7a6090 1 1 -------- logfg02 sys dic 5 os----u 3a765d6d 85 99 -------- logfg03 sys dic 2 os----u 3a765d6d 100 109 -------- logfg04 sys dic 3 os----u 3a765d6d 110 121 -------- logfg05 sys dic 3 os----u 3a765d6d 122 130 --------

   pdlogatul -d sys -s dic -i HOSTNAME : dbhost1(152953) SERVER_NAME:dic AUTO_LOG_UNLOAD NOW_UNLOAD_LOG_GROUP CREATE_DIR ACTIVE **** /unload_dir CURRENT LOG GENERATION INFO. LOG_GROUP GEN_NO. SERVER_RUN_ID RUN_ID UNLOAD_FILE_NAME logfg01 1 3a7a60ae 3a7a6090 dic_3a7a60ae0007_logfg01

   From the above results, record the following types of information for the current system log file (the underlined areas):
   
   • Server name: dic
   • File group name: logfg01
   • Server run ID: 3a7a60ae
   • Generation number: 1
   What must be checked here is the server run ID (SERVER_RUN_ID). Do not confuse it with the run ID (RUN_ID).