HP P6000 Cluster Extension Software Administrator Guide (5697-2274, November 2012)
link(s) is re-established. The amount of delta data to be transferred between the source and
destination vdisk could be large enough for the copy process to take some time.
• To prevent the failover timeout trigger from terminating a failover command before it is finished,
the time to copy an average amount of daily processed (write) data should be measured and
the resource online timeout interval should be adjusted accordingly. Use only one (the slowest)
link used for P6000 Continuous Access to measure the copy time. This ensures that the average
daily generated data can be transferred fast enough from the remote P6000/EVA storage
system, even in the event of a single surviving replication link between the P6000/EVA storage
systems.
In general, because the failover environment is dispersed into two (or more) data centers, the
failover time cannot be expected to be the same as it would be in a single data center with a single
shared disk device.
Restrictions for customized implementations
The following restrictions apply when using the P6000 Cluster Extension CLI:
• The P6000 Cluster Extension CLI command clxevarun must be invoked before the associated
disk resources are activated.
• Associated disk resources must not be activated on any other system. If other disk resources
are activated, P6000 Cluster Extension may remove write-access rights for those disk devices
(putting them in read-only mode).
Command-line utilities
Command-line utilities are also included with P6000 Cluster Extension to allow configuration of
P6000 Cluster Extension on all platforms for both the CLI (clxevarun) and cluster integration.
clxconf
Description Use clxconf to manually retrieve the consistency set object paths for a DR
group and place them in a file called clxobjectpaths.cfg located in the
P6000 Cluster Extension conf directory %HPCLX_EVA_PATH%.
clxconf is used as part of the P6000 Cluster Extension configuration process
for the CLI integration. After clxconf places information in
clxobjectpaths.cfg, that information must be copied to UCF.cfg and
the P6000 Cluster Extension resource configuration file.
Syntax clxconf –smis
Operands Required parameter for clxevarun-smis
Example 1
clxevarun configuration
# clxconf -smis
In this example, clxconf assumes that one or more APPLICATION tags are
defined in the UCF.cfg file and have specified all necessary objects, including
the DeviceGroup object, to map the DR group to the application service.
---- Sample UCF.cfg begin
APPLICATION CLX030
DeviceGroup \Data Replication\DRG030 #DR group
DC_A_StorageCellWWN 50001FE15002B5A0
DC_B_StorageCellWWN 50001FE15002B570
DC_A_ManagementHosts smam019fk351k # active sma
DC_B_ManagementHosts clxeva1 # passive sma
FailsafeMode disable
DC_A_Hosts w2k7 w2k6
DC_B_Hosts w2k5 w2k8
APPLICATION CLX031
56 CLI commands and utilities