Error reporting communications (erc) – HP XP P9500 Storage User Manual

Page 32

Advertising
background image

Error reporting communications (ERC)

Error reporting communications (ERC) transfers information between host processors at the primary
and secondary sites. It is a critical component of any disaster recovery effort. You can configure
ERC using channel-to-channel communications, NetView technology, or other interconnect
technologies, depending on your installation requirements and standards. Neither Continuous
Access Journal Z nor Remote Web Console provides ERC between the primary and secondary
sites.

When Continuous Access Journal Z is used as a data migration tool, ERC is recommended, but
not required. When it is used as a disaster recovery tool, ERC is required to insure effective disaster
recovery operations. When a pair is suspended due to an error condition, the primary system
generates sense information which results in an IEA491E system console message. This information
should be transferred to the primary site via the ERC for effective disaster detection and recovery.

Sharing volumes with Continuous Access Synchronous Z, other program
products

Continuous Access Journal Z volumes can be shared with other program product volumes. Sharing
pair volumes results in enhanced replication solutions, for example when Continuous Access Journal
Z and Continuous Access Synchronous Z or Business Copy Z volumes are shared.

For planning information, see the following:

“Continuous Access Journal Z configurations with Continuous Access Synchronous Z” (page 130)

“Continuous Access Journal Z configurations with Business Copy Z” (page 141)

“Sharing Continuous Access Journal Z volumes ” (page 126)

for the following program products:

Virtual LVI

Cache Residency Z

Planning for Continuous Access Journal Z with multiple P9500 systems

A Continuous Access Journal Z system can be configured with up to four primary P9500 systems
and four secondary P9500 system. Any combination of primary and secondary systems, from one
to four, may be used.

Figure 4 (page 33)

shows an example configuration with multiple primary

and secondary systems.

32

Planning volumes, systems

Advertising