Nonstop Database, HiRDB Version 9 Disaster Recovery System Configuration and Operation Guide

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

2.5.3 Points to consider when designing paired logical volume groups

Organization of this subsection
(1) Naming rules
(2) Correspondence with paired logical volumes
(3) Configuration example

(1) Naming rules

Assign names to paired logical volume groups according to the naming rules described in the following table.

Table 2-7 Naming rules for paired logical volume groups

File classification Real Time SAN Replication processing method
All synchronous or hybrid method All asynchronous method
DB aaaa_bb....bb_DB aaaa_ALL
Assign a single paired logical volume group to all file classifications.
LOG aaaa_bb....bb_LOG
SPD aaaa_bb....bb_SPD
USTS aaaa_cccc_USTS
SSTS aaaa_bb....bb_SSTS

Legend:
aaaa: HiRDB identifier
bb....bb: Server name
cccc: Unit identifier

(2) Correspondence with paired logical volumes

In the all synchronous and hybrid methods, if paired logical volumes are designed correctly, the file classifications of the files located in the paired logical volumes, and the units and servers that use these files, will all be identical. If file classifications, or the units or servers used, are different, check the notes in 2.4.2 Notes on creating HiRDB file system areas.

(3) Configuration example

Place the update-copy target files (HiRDB file system area) on a paired logical volume group (paired logical volume). The following figure shows a configuration example of file locations using the all synchronous or hybrid method.

Figure 2-1 File location configuration example

[Figure]

Legend:
HRD1: HiRDB identifier
UNT1: Unit identifier
sds1: Server name
RD: User RDAREA file
MAST: Master directory RDAREA file
DDIC: Data dictionary RDAREA file
LOG: System log file
SPD: Synchronization point dump file
SSTS: Server status file
USTS: Unit status file
Hint
  1. Generate a paired logical volume group for each server (or unit) that uses file classifications and files.
  2. Position update-copy target files in a paired logical volume group in which the file classification matches the server (or unit) that uses files.
  3. You cannot position files whose file classification does not match the server that uses files in the same paired logical volume group.

Correspondence relationship
  1. A paired logical volume group consists of multiple paired logical volumes.
  2. Each paired logical volume corresponds to a single paired volume.
  3. Each paired volume corresponds to a single HiRDB file system area.
  4. Multiple files can be stored in a single HiRDB file system area.