Bcm Specifications - HP XP P9500 User Manual

Table 2 General system requirements (continued)
Item
Logical paths
Maximum number of
remote systems
Pair volumes
Number of pairs
Disk Track Format
Error Reporting
Communications (ERC)
software
Continuous Access
Synchronous Z Interfaces

BCM specifications

Pair operations may be performed using BCM commands from the host system to the disk array.
With BCM commands, you can add, suspend, resynchronize, and delete pairs, as well as monitor
pair status. You can also create the Continuous Access Synchronous Z association between main
and remote system (add RCU).
14 Requirements and specifications
Requirement
Maximum of eight from main disk array to remote disk array.
Logical paths are established for main and remote disk array CUs separately.
Maximum number of logical paths allowed for a disk array is 32 (8 paths per remote
system X 4 remote systems per main system).
Maximum of four remote systems per main system.
Each remote system CU must be added separately to a main system.
M-VOL and R-VOL must be the same size and emulation.
One M-VOL may only be copied to one R-VOL.
M-VOL and R-VOL can be shared with other program product volumes. See
types that can be shared with Continuous Access Synchronous Z" (page
See "Planning volume pairs" (page 29)
Limited per P9500 system. See
Must be insured by the user. The track format for the M-VOL and R-VOL must meed the
following requirements:
The M-VOL and R-VOL must have the same track format.
Record zero (R0) must be standard format, with key length of zero and data length of
eight. The main system aborts the initial copy operation if R0 is not standard format.
The CCHH (logical cylinder address and logical head address) of R0 must be identical
to the physical cylinder address and physical head address of the track.
The CCHH of each user record in a track must be unique.
Required for disaster recovery.
Recommended for data migration.
See "Error reporting communications" (page 37)
Remote Web Console
◦ Required.
◦ Storage Administrator (Remote Copy) role is required.
◦ The main system must be LAN-attached to a Remote Web Console computer.
◦ The remote system should be attached using a separate LAN at the remote site.
BCM
◦ Optional.
◦ Command device required.
See "BCM specifications " (page
PPRC
◦ Optional.
See "PPRC specifications, restrictions " (page
on for more information.
"Maximum number of pairs supported" (page
for more information.
14).
17).
"Volume
39).
31).