![[Contents]](FIGURE/CONTENT.GIF)
Nonstop Database, HiRDB Version 9 Disaster Recovery System Configuration and Operation Guide
![[Index]](FIGURE/INDEX.GIF)
![[Back]](FIGURE/FRONT.GIF)
![[Next]](FIGURE/AFTER.GIF)
Specify the paired logical volume groups in the RAID Manager's config file (HORCM_CONF). The following table shows the items that are associated in the RAID Manager's config file.
Table 3-1 Items associated in RAID Manager's config file
| Item name | RAID Manager's config file (HORCM_CONF) |
|---|---|
| Pair logical volume | HORCM_DEV dev_name parameter |
| Pair logical volume group | HORCM_DEV dev_group parameter |
Start the RAID Manager instances, built in (1) RAID Manager's config file, at both the main and remote sites. To start the RAID Manager instances, use RAID Manager's horcmstart command. For details about the horcmstart command, see the RAID Manager documentation.
Using RAID Manager's paircreate command, generate paired logical volume groups. During this process, specify the volume at the main site in the P-VOL operand. For details about the paircreate command, see the RAID Manager documentation.
The fence level (the value of the -f option) you specify when executing the paircreate command differs depending on the Real Time SAN Replication processing method (the value of the pd_rise_pairvolume_combination operand) and the protection mode (the value of the pd_rise_fence_level operand). The following table shows these relationships.
Table 3-2 Fence level to be specified when executing the paircreate command
| Real Time SAN Replication processing method (value of the pd_rise_pairvolume_combination operand) | Protection mode (value of the pd_rise_fence_level operand) | Pair logical volume group name | Fence level (value of the -f option of the paircreate command) |
|---|---|---|---|
| sync | data | aaaa_bb....bb_DB | data |
| aaaa_bb....bb_LOG | |||
| aaaa_cccc_USTS | |||
| aaaa_bb....bb_SSTS | |||
| aaaa_bb....bb_SPD | |||
| never | aaaa_bb....bb_DB | never | |
| aaaa_bb....bb_LOG | |||
| aaaa_cccc_USTS | |||
| aaaa_bb....bb_SSTS | |||
| aaaa_bb....bb_SPD | |||
| async | -- | aaaa_ALL | async |
| hybrid | data | aaaa_bb....bb_DB | async |
| aaaa_bb....bb_LOG | data | ||
| aaaa_cccc_USTS | |||
| aaaa_bb....bb_SSTS | |||
| aaaa_bb....bb_SPD | |||
| never | aaaa_bb....bb_DB | async | |
| aaaa_bb....bb_LOG | never | ||
| aaaa_cccc_USTS | |||
| aaaa_bb....bb_SSTS | |||
| aaaa_bb....bb_SPD |
The consistency group you specify when creating an asynchronous paired volume also differs depending on the Real Time SAN Replication processing method (the value of the pd_rise_pairvolume_combination operand). The following table shows this relationship.
Table 3-3 Consistency group (value of the -f option) to be specified when executing the paircreate command
| Real Time SAN Replication processing method (value of the pd_rise_pairvolume_combination operand) | Pair logical volume group name | Consistency group ID (value of the -f option of the paircreate command) |
|---|---|---|
| sync | There is no asynchronous paired volume. | |
| async | aaaa_ALL | Assign all HiRDB paired logical volume groups inside the HiRDB system to the same consistency group. |
| hybrid | aaaa_bb....bb_DB | Assign individual paired logical volume groups to different consistency groups. |
An example of creating a paired logical volume group is described below. The following system configuration is assumed.
set pd_system_id = HRD1 set pd_rise_use = Y set pd_rise_pairvolume_combination = hybrid set pd_rise_fence_level = data pdunit -u UNT1 -x host1 -d "/opt/HiRDB_S" pdstart -t SDS -s sds1 -u UNT1 |
paircreate command execution example (executed from the main site)
paircreate -g HRD1_sds1_DB -f async -vl paircreate -g HRD1_sds1_LOG -f data -vl paircreate -g HRD1_UNT1_USTS -f data -vl paircreate -g HRD1_sds1_SSTS -f data -vl paircreate -g HRD1_sds1_SPD -f data -vl |
All Rights Reserved. Copyright (C) 2011, Hitachi, Ltd.