User's Guide

11. Restart the Raid Manager instance so that the new information in the configuration file is read.
# horcmshutdown.sh <instance-#>
# horcmstart.sh <instance-#>
12. Repeat these steps on each host that will run this particular application package. If a host may
run more than one application package, you must incorporate device group and host
information for each of these packages.
Note that the Raid Manager configuration file must be different for each host, especially for
the HORC_MON and HORC_INST fields.
13. If not previously done, create the paired volumes.
# paircreate -g <devgroup> -f <fencelevel> -vl -c 15
This command must be issued before creating volume groups. For creating a pair of journal
groups, refer to the next section, “Pair Creation of Journal Groups”.
CAUTION: Paired devices must be of compatible sizes and types.
When using the paircreate command to create PVOL/SVOL Continuous Access pairs,
specify the -c 15 switch to ensure the fastest data copy from PVOL to SVOL.
Pair Creation of Journal Groups
The Continuous Access Journal has the same characteristic as Continuous Access Asynchronous
such that Raid Manager controls Continuous Access Journal similar to Continuous Access
Asynchronous.
The Raid Manager configuration of the device group pair for Continuous Access Journal is exactly
the same as the configuration of the Continuous Access Asynchronous device group pair. In the
/etc/horcm0.conf file, do not specify any journal volumes or journal group number. Only data
volumes (device group and it’s devices) need to be in the configuration file.
Creating Continuous Access Journal Pair
To create a journal group pair, use the paircreate command.
# paircreate -g <device_group> -f async -vl -c 15 -jp <id> \ -js <id>
Similar to Continuous Access Asynchronous, the fence “async” must be assigned to the command
with two additional options -jp and -js.
-jp <id> : This option is to specify a journal group ID for PVOL
-js <id> : This option is to specify a journal group ID for SVOL
The -jp and -js options are required if the device group is configured to use Continuous Access
Journal. The <id>used with -jp and -js option do not need to be the same.
Sample Raid Manager Configuration File
The following is an example of a Raid Manager configuration file for one node (ftsys1).
## horcm0.conf.ftsys1- This is an example Raid Manager configuration
file for node ftsys1.Note that this configuration file is for Raid
Manager instance 0, which can be determined by the "0" in the filename
"horcm0.conf".
#Whenever this configuration file is changed, you must stop and restart
the instance of Raid Manager before the changes will be recognized.
This can be done using the following commands:# horcmshutdown.sh
<instance># horcmstart.sh <instance># After restarting the Raid Manager
instance, you should confirm that there are no configuration errors
reported by running the pairdisplay command with the "-c" option.
Preparing the Cluster for Data Replication 167