HP XP P9000 for Business Continuity Manager Software Release Notes
Table Of Contents
- HP XP P9000 for Business Continuity Manager Software 7.6.0-00
- Description
- Operating systems
- License keys
- Product models
- Devices supported
- Languages
- New features and important enhancements
- Prerequisites
- Prerequisite programs
- Related programs
- Memory and disk space requirements
- Virtual memory space requirements
- Fixes
- Resolved issues
- Installation instructions
- Installation precautions
- Determining current version
- Version description
- User SVC version that corresponds to this product version
- Compatibility/interoperability
- System configuration
- Remote DKC control function
- Copy types
- Other
- Temporary restrictions
- Specification differences from previous versions
- 4x4x4 Multi-Target configuration with Delta Resync
- Overview of CLI commands for 4x4x4 Multi-Target configuration with Delta Resync
- Documentation feedback
Compatibility/interoperability
System configuration
• BCM supports 2DC configurations (1:1). By making multiple units of 2DC configurations, it is
possible to create N:N configurations.
• BCM supports 3DC (Cnt Ac-S and Cnt Ac-J) configurations (Cascade configurations and Multi-Target
configurations). Note that 3DC configurations are supported only when all storage systems in the
configurations are XP10000/XP12000 disk arrays, XP20000/XP24000 disk arrays, or XP P9500
disk arrays. N:1 configuration and a configuration that consists of 4 or more DCs are not
supported.
• BCM supports 4x4 and 4x4x4 Multi-Target configurations. Note that the configuration should
consist entirely of XP10000/XP12000 disk arrays, XP20000/XP24000 disk arrays, or XP P9500
disk arrays.
• BCM supports 4x4x4 Cascade configurations. Note that the configuration should consist entirely
of XP12000/XP10000 disk arrays, XP24000/XP20000 disk arrays, or XP P9500 disk arrays.
Remote DKC control function
• When using Remote DKC control function, use Fibre Channel links for connection between DKCs.
ESCON links are not supported. When you define the logical path between CUs for Remote DKC
control function, you must define the path between the CUs that belong to the command device
volumes.
• To share a command device among multiple operating systems, ensure that the &YKCMDIF variable
is either defined in the IEASYM member or set by the START YKSETENV command.
• When allocating a command device, note the following items:
Parity group cannot be moved if a command device is defined within the parity group.◦
◦ Parity group type cannot be changed if the command device is defined within the parity
group.
◦ The command device between LCUs cannot be moved.
◦ The volume size of the command device cannot be changed (550 cylinders are required for
XP128 or XP1024 disk arrays).
• When defining a multiple command device line, HP recommends the following command device
setting to reduce the CLI command response time:
◦ The number of command devices for a head storage system of a route list should be 17 or
less.
Copy types
There should not be a mix of copy types within a single copy group. Ensure that all volumes are
SIMPLEX in the initial state. BCM does not display the pair status correctly in the following conditions:
• Copy group definition is changed when not all pairs are SIMPLEX.
• Pair configuration in copy group definition differs from the actual pair configuration.
Compatibility/interoperability 9