16.2.4 Storage configuration
When you use the multi-node function, provide the following file systems and disks.
-
Node-local file system
In Figure 16‒1: Example of a system configuration using the multi-node function, LOC001 to LOC003 are node-local file systems.
-
File system inherited at node switchover
In Figure 16‒1: Example of a system configuration using the multi-node function, FS001 and FS002 are file systems inherited at node switchover.
-
Disks for DB area files
In Figure 16‒1: Example of a system configuration using the multi-node function, LU001 to LU005 and WRK001 to WRK003 are disks for DB area files.
Note that some file systems and disks require device names that allow the disk to be identified on each node. If the path between the server and storage is a single-path configuration, we recommend that you use WWNs. When implementing redundant paths between server and storage, the device name will differ according to the redundancy method being used. Examples of device names in Figure 16‒1: Example of a system configuration using the multi-node function are as follows:
-
Examples of device names in single-path configuration
FS001: /dev/disk/by-id/wwn-0x600605b0041db9c016ea34c3b1b53e0a
FS002: /dev/disk/by-id/wwn-0x600605b0041db9c016ea34c3b1b6c44d
LU001: /dev/disk/by-id/wwn-0x600605b0041db9c016ea34c3b1b828e9
LU002: /dev/disk/by-id/wwn-0x600605b0041db9c016ea34c3b1b7d9fd
LU003: /dev/disk/by-id/wwn-0x600605b0041db9c016ea34c3b1b87793
LU004: /dev/disk/by-id/wwn-0x600605b0041db9c016ea34c3b1b8c6d3
LU005: /dev/disk/by-id/wwn-0x600605b0041db9c016ea34c3b1b9160f
-
Examples of device names in redundant configuration using multipath software (DMMP)
FS001: /dev/mapper/mpath1
FS002: /dev/mapper/mpath2
LU001: /dev/mapper/mpath11
LU002: /dev/mapper/mpath12
LU003: /dev/mapper/mpath13
LU004: /dev/mapper/mpath14
LU005: /dev/mapper/mpath15
- Organization of this subsection
(1) Node-local file system
A node-local file system stores the following directories:
-
Server directory
To create a server directory, use the adbinstall command.
-
DB directory
For details about how to create the DB directory, see 16.3.8 Creating a database.
-
Multi-node synonym dictionary storage directory
For details about the multi-node synonym dictionary storage directory, see (6) Creating the multi-node synonym dictionary storage directory in 16.24.1 Preparing for synonym search operations.
-
Audit trail directory
For details about the audit trail directory, see 2.18.5 Output destination of audit trails (audit trail file).
-
Output-directory for common format audit trails
For details about the output-directory for common format audit trails, see 2.18.9 Conversion of audit trail information (linkage with JP1/Audit Management - Manager).
In Figure 16‒1: Example of a system configuration using the multi-node function, LOC001 to LOC003 are node-local file systems.
-
LOC001
Local file system of server machine hadb01 (master node)
-
LOC002
Local file system of server machine hadb02 (slave node)
-
LOC003
Local file system of server machine hadb03 (slave node)
(2) File systems inherited at node switchover
Configure the following file systems as file systems inherited at node switchover:
-
File system for the system directory which stores the content of ADBSYS under the DB directory
-
File system that stores synonym dictionary files
Create these file systems inherited at node switchover on an LV in a VG that consists of disks (shared disks) that can be referenced from all nodes. For details about shared disks, see Shared disk configuration in the manual HA Monitor for Linux(R) (x86).
In Figure 16‒1: Example of a system configuration using the multi-node function, FS001 and FS002 are the file systems inherited at node switchover.
-
FS001
File system for the system directory
Here, the name of the VG is vg_hadb, and the name of the LV is hadb_sys.
-
FS002
File system that stores synonym dictionary files
In this example, the name of the VG is vg_hadb02, and the name of the LV is hadb_syndict. If you do not intend to conduct synonym searches, the file system that stores synonym dictionary files is not required.
- Important
-
When using SCSI reservation for shared disk, configure the disks where the file systems inherited at node switchover are created as subject to SCSI reservation. On disks subject to SCSI reservation, do not create any areas other than file systems inherited at node switchover.
(3) Disks for DB area files
Provide a disk for each DB area file.
For the DB area files listed below, allocate a block special file. Also, make sure that disks that correspond to block special files can be referenced from all nodes.
-
Master directory DB area file
-
Dictionary DB area file
-
System-table DB area file
-
Data DB area file
- Important
-
When using SCSI reservation for shared disk, configure the disks that store the preceding DB area files as subject to SCSI reservation.
Provide the disk that is used by the following DB area file on each node:
-
Work table DB area file
- Important
-
-
If a disk that needs to be prepared for each node (disk to store the work table DB area files) is shared and used by multiple nodes, operations are not guaranteed. Incorrect retrieval results might be displayed, or the HADB server might terminate abnormally.
-
When using SCSI reservation for shared disk, do not configure the disks on which work table DB area files are stored as subject to SCSI reservation.
-
In Figure 16‒1: Example of a system configuration using the multi-node function, LU001 to LU005 and WRK001 to WRK003 are the disks for DB area files.
-
LU001
DB area disk that comprises a dictionary DB area
-
LU002
DB area disk that comprises a master directory DB area
-
LU003
DB area disk that comprises a system-table DB area
-
LU004
DB area disk that comprises a data DB area (ADBUTBL01)
-
LU005
DB area disk that comprises a data DB area (ADBUIDX01)
-
WRK001
DB area disk that comprises the work table DB area of the HADB server on server machine hadb01 (master node)
This is a node-local disk. The name of the corresponding block special file is set to /dev/mapper/WRK001.
-
WRK002
DB area disk that comprises the work table DB area of the HADB server on server machine hadb02 (slave node)
This is a node-local disk. The name of the corresponding block special file is set to /dev/mapper/WRK002.
-
WRK003
DB area disk that comprises the work table DB area of the HADB server on server machine hadb03 (slave node)
This is a node-local disk. The name of the corresponding block special file is set to /dev/mapper/WRK003.