
Chapter 7, Extended Frozen Image Services (Array Integration Option) 103
Configuring Primary and Secondary Disks
◆ Target ID: the SCSI or fibre channel target ID number of the disk, configured by
means of the array’s dedicated console (not from a NetBackup host).
◆ LUN: the SCSI or fibre channel logical unit number of the disk, configured by means of
the array’s dedicated console (not from a NetBackup host).
◆ MU: a numeric mirror descriptor for cascading disks (default 0). If you are not using
cascading disks, this value may be left blank. A cascading disk has more than one
mirror (secondary) associated with a given primary.
HORCM_INST
Enter values for the following:
◆ dev_group: same as under HORCM_DEV.
◆ partner host: the host where the corresponding secondary (or primary)
configuration file resides (may be the same as the host specified under HORCM_MON).
For this example, the host and partner host are both turnip. (See under “partner
service” for a discussion of partner.)
◆ partner service: the port name of the RAID Manager instance for the
corresponding secondary (or primary) configuration file, to be registered in the
/etc/services file.
For the example /etc/horcm0.conf file, the partner service for horcmgr0 (entered
under HORCM_MON, service) is horcmgr1. For the secondary-disk configuration
example /etc/horcm1.conf file (below), the partner service is the opposite:
horcmgr0.
Partner is a relative term. From the viewpoint of the configuration file for the primary
disks (/etc/horcm0.conf file), the partner file would be /etc/horcm1.conf (for
the secondary disks). It is the same with partner service and partner host: each refers
to the secondary from the viewpoint of the primary, or to the primary from the
viewpoint of the secondary.
Note The partner service value must be entered in the /etc/services file.
Comentarios a estos manuales