Nonstop Database, HiRDB Version 9 Disaster Recovery System Configuration and Operation Guide
When you use the hybrid method, the updated data on all paired logical volume groups used by the server that collects the synchronization point dump is collected in the dump so that the database at the remote site can be recovered from the synchronization point as well. If an update copy error occurs in the paired logical volume group in which RDAREAs are created and the protection mode is data and the status of the paired logical volume group is not PAIR, the updated data for all paired logical volume groups cannot be synchronized, and so the collection of synchronization point dumps is stopped, and the KFPS02178-E message is output.
The following table shows how synchronization point dumps are collected when using the hybrid method.
Table 6-2 How synchronization point dumps are collected when using the hybrid method
| Protection mode | Status of the paired logical volume group in which RDAREAs are created | Collection of synchronization point dump at the main site | Switching sites after a synchronization point dump is collected at the main site |
|---|---|---|---|
| data | PAIR | Completes the dump. | You can switch sites without data discrepancies. |
| Not PAIR | Stops the dump. | ||
| never | PAIR | Completes the dump. | |
| Not PAIR | In normal start, because data discrepancies occur, switching sites is prohibited. In restart, because HiRDB cannot be started, switching sites cannot be executed. |
The following table what HiRDB does when the collection of a synchronization point dump stops at the main site.
Table 6-3 What HiRDB does when the collection of a synchronization point dump stops at the main site
| Process timing | Start or termination type | What HiRDB does after the collection of synchronization point dump stops at the main site | Action you need to take when the error occurs |
|---|---|---|---|
| During startup processing |
|
Outputs the abort code Pstj14j and stops HiRDB startup processing. | Change the status of the paired logical volume group in which the RDAREAs used by the applicable server are created to PAIR and then restart HiRDB. |
| Restart | Continues HiRDB startup processing. | Change the status of the paired logical volume group in which the RDAREAs used by the applicable server are created to PAIR and then collect a synchronization point dump by executing the pdlogsync command. | |
| Restart following planned termination | |||
| During termination process | Normal termination | Stops HiRDB termination processing, outputs the abort code Pstj14k, and abnormally terminates HiRDB (or a unit for HiRDB/Parallel Server). | Change the status of the paired logical volume group in which the RDAREAs used by the applicable server are created to PAIR, restart HiRDB (or the unit), and then terminate HiRDB normally. |
| Planned termination | Change the status of the paired logical volume group in which the RDAREAs used by the applicable server are created to PAIR, restart HiRDB (or the unit), and re-execute planned termination of HiRDB. | ||
| Forced termination | Continues HiRDB termination processing. | No action required | |
| During operation | -- | Continues processing. | Change the status of the paired logical volume group in which the RDAREAs used by the applicable server uses are created to PAIR and then collect a synchronization point dump by executing the pdlogsync command. |
All Rights Reserved. Copyright (C) 2011, Hitachi, Ltd.