Nonstop Database, HiRDB Version 9 System Operation Guide

[Contents][Index][Back][Next]

6.4.7 Example 7 (backing up a server)

All RDAREAs in a back-end server (bes1) are backed up during operation of a server in a HiRDB parallel server configuration. A log point information file is also obtained, because the system is operating without unloading the system log.

Organization of this subsection
(1) Using the pdlogswap command to swap the system log files in the server that is to be backed up
(2) Using the pdcopy command to back up the entire server

(1) Using the pdlogswap command to swap the system log files in the server that is to be backed up

System log files are swapped in order to physically separate the system logs required for database restoration. To restore the RDAREAs from the backup copy to be created in step (2), the system log collected subsequently (the system log in the file to be used as the current file after swapping) will be used as input information.

 
pdlogswap -d sys -s bes1 -w
 

(2) Using the pdcopy command to back up the entire server

 
pdcopy -m /rdarea/mast/mast01 -M r -s bes1 -b /pdcopy/backup01
-z /pdcopy/logpoint01 -p /pdcopy/list01
 

Explanation
-m: Specifies the name of the first HiRDB file in the master directory RDAREA.
-M: Specifies the referencing-permitted mode as the backup acquisition mode.
-s: Specifies that all RDAREAs under the 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. Specify this option when operation without unloading the system log or the automatic log unloading facility is used.
-p: Specifies the output file name for the pdcopy command's processing results listing.

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.