Configuring the /etc/horcm.conf File on the Nodes of the Primary Cluster

On each storage-attached node of the primary cluster, you configure Hitachi TrueCopy and Universal Replicator device groups as properties of the HORCM_DEV or HORCM_LDEV parameter in the /etc/horcm.conf file, and associate them with LUNs and, if appropriate, journal volumes. All devices that are configured in this file, including journal volumes, must be in locally attached storage. The /etc/horcm.conf file is read by the HORCM daemon when it starts, which occurs during reboot or when the Sun Cluster Geographic Edition software is started. If you change the /etc/horcm.conf file on any node after the Sun Cluster Geographic Edition software is started, and you do not anticipate rebooting, you must restart the HORCM daemon on that node by using the commands:

phys-paris-1# horcm-installation-directory/usr/bin/horcmshutdown.sh
phys-paris-1# horcm-installation-directory/usr/bin/horcmstart.sh

Table 1-2 shows the configuration of one journaling Hitachi Universal Replicator device group in the /etc/horcm.conf file as a property of the HORCM_LDEV parameter. Each LUN in the device group is described on a single line consisting of four space-delimited entries. The LUNs in the devgroup1 device group are named pair1 and pair2. The administrator chooses the device group and paired device names. In the third field of the file, each LUN is described by its serial number, followed by a colon, followed by the journal ID of its associated journal volume. In the logical device number (ldev) field, the controller unit (CU) is followed by a colon, which is followed by the logical device number. Both values are in hexadecimal format. All entries are supplied by the raidscan command, which is described in more detail in Hitachi's documentation. The ldev value that is supplied by the raidscan command is in decimal format, so you must convert the value to base 16 to obtain the correct format for the entry in the ldev field. You can only use the configuration shown in Table 1–2 with Hitachi Universal Replicator, as Hitachi TrueCopy does not support journaling.

If you want to ensure the consistency of replicated data with Hitachi Universal Replicator on both the primary cluster and the secondary cluster, you must specify a journal volume ID in the third property configuration field of HORCM_LDEV for each device in a Hitachi Universal Replicator device group. Otherwise, journaling does not occur and Hitachi Universal Replicator's functionality in Sun Cluster Geographic Edition configurations is no greater than the functionality of Hitachi TrueCopy.

Table 1–3 shows the configuration of one non-journaling Hitachi TrueCopy or Universal Replicator device group in the /etc/horcm.conf file as a property of the HORCM_DEV parameter. Each LUN in the device group is described on a single line consisting of five space-delimited entries. The table describes a device group named devgroup2 that is composed of two LUNs in a single shared storage array that is attached to the nodes of the primary cluster. The LUNs have the device names pair3 and pair4 and are designated by their port, CL1-A, target 0, and LU numbers, 3 and 4. The port number, target ID, and LU numbers are supplied by the raidscan command, which is described in more detail in Hitachi's documentation. For Hitachi TrueCopy and Universal Replicator, there is no entry in the MU number field.