Items
Notes and restrictions
Hot standby
operations
Note the following when executing hot standby operations using
industry-standard failover products (for example, MC/ServiceGuard,
HACMP, FirstWatch
®
) and TrueCopy/ TrueCopy Async/ Universal
Replicator.
•
Do not split a single volume using partitions and share it among
different server programs. If you do so, the takeover command
is executed for the volume when failover of a server program
happens, and that might affect other servers that share the
volume.
•
If you are using the LVM, do not create LDEVs for different LVM
within the same volume. If you do so, the takeover command is
executed for the volume when failover of a server program
happens, and that might affect other servers that share the
volume.
Coexistence of LVM
mirror and
TrueCopy
When the LVM mirror and TrueCopy volumes are used together, the
LVM mirror handles write errors and changes the volumes. Thus,
the fence level of the volumes used by the LVM mirror must be set
to
data
.
Using paired
volume in a single
host
When constructing paired volume in a single host, it is necessary to
activate two or more CCI instances. To activate two or more CCI
instances, instance numbers must be assigned using the
environment variable
HORCMINST
. The HORCM and TrueCopy/
ShadowImage commands must possess this environment variable.
A configuration definition file and a log directory is set for each
instance. For sharing command devices over 17 instances, use LU
path among the storage system ports to share the command
devices.
Sharing volumes in
a hot standby
configuration
When paired volume is used for the disk shared by the hosts in hot
standby configuration using HA software, use the primary volume as
the shared disk and describe the corresponding hosts using the
paired volume in the configuration definition file as shown below. In
the HA configuration, if a TrueCopy command issued by host C fails
in host B (because host B has gone down and/or IO_ERROR of the
command device), host A is connected and the command execution
is retried.
9-4
Troubleshooting
Command Control Interface User and Reference Guide
Summary of Contents for HUS VM
Page 10: ...x Command Control Interface User and Reference Guide ...
Page 18: ...xviii Preface Command Control Interface User and Reference Guide ...
Page 78: ...2 50 CCI software environment Command Control Interface User and Reference Guide ...
Page 154: ...4 8 Starting up CCI Command Control Interface User and Reference Guide ...
Page 191: ...Provisioning operations with CCI 5 37 Command Control Interface User and Reference Guide ...
Page 280: ...6 56 Data replication operations with CCI Command Control Interface User and Reference Guide ...
Page 286: ...6 62 Data replication operations with CCI Command Control Interface User and Reference Guide ...
Page 302: ...7 16 Data protection operations with CCI Command Control Interface User and Reference Guide ...
Page 324: ...8 22 Examples of using CCI commands Command Control Interface User and Reference Guide ...
Page 524: ...9 200 Troubleshooting Command Control Interface User and Reference Guide ...
Page 529: ...Command Control Interface User and Reference Guide ...