HP XP Continuous Access Software - Manual (Page 191)

you must prepare a total of four RAID Manager XP configuration files, assuming one instance per NAS
package. For two instances, you need a total of eight configuration files.
In NAS Blade, you can define one or two RAID Manager XP instances per NAS package. To operate
only the Continuous Access XP Journal pairs in RAID Manager XP, you need one instance. To operate
pairs where Continuous Access XP Journal and Business Copy XP are cascaded, you need two instances.
The following section explains how to create a RAID Manager XP configuration definition file using the
NAS Blade system with LUs as an example (see Figure 74 ).
Figure 74 Example of configuring a pair LU
Adding the HORCM_DEV and HORCM_INST sections using the mkconf.sh command in RAID Manager XP
Add the HORCM_DEV and HORCM_INST sections to the template of the RAID Manager XP configuration
definition file using the mkconf.sh command in RAID Manager XP.
Table 36 Adding the HORCM_DEV and HORCM_INST sections (for Instance number 16)
$ cat /home/nasroot/horc_devfile | sudo mkconf.sh -gg Device Group Name -i
16 -a
CAUTION:
If you execute the mkconf.sh command without specifying the -a option, the HORCM_MON and
HORCM_CMD sections in the RAID Manager XP configuration definition file that are automatically
created when NAS Backup Restore is installed are overwritten. In this case, delete all lines above the
HORCM_MON section, and change the entry service in the HORCM_MON section to an appropriate
value based on Table 38 .
To execute the mkconf.sh command, the LU constituting the file system to be paired must be attached to
the NAS OS. The LU configuration (size and number) in the file system to be paired must be exactly the
same in the primary and secondary sites.
Continuous Access XP Journal user guide 191