HP P9000 Replication Manager Software 7.4.0-00 Configuration Guide (TB584-96058, December 2012)
• If you are replacing an instance of P9000 mainframe agent with HP StorageWorks P9000 for
Business Continuity Manager, HP recommends removing P9000 mainframe agent first.
Prerequisites for managing copy pairs on mainframe systems using P9000 RAID
Manager
With P9500 systems, you can manage volumes and copy pairs on mainframe systems using P9000
RAID Manager. In this case, you must use the views and the copy pair definition wizard for open
systems. The prerequisites are as follows:
• The copy pair must consist of Continuous Access Synchronous or Continuous Access Journal.
• Multi-target and cascade configurations cannot be used.
• Neither a virtual command device nor a device group is used.
• The copy pair is not simultaneously managed by P9000 RAID Manager and HP StorageWorks
P9000 for Business Continuity Manager. That is:
• A copy pair managed by HP StorageWorks P9000 for Business Continuity Manager is not
defined in the configuration definition file of P9000 RAID Manager.
• No volumes that consist of a copy pair in a mainframe system managed by P9000 RAID
Manager are scanned by HP StorageWorks P9000 for Business Continuity Manager, and HP
StorageWorks P9000 for Business Continuity Manager is not aware of LDEVs that comprise
the same copy pair.
• The value of server.agent.rm.centralizePairConfiguration in the server.prop-
erties file of Device Manager Agent must be set to enable. For details, see the HP P9000
Command View Advanced Edition Suite Software Administrator Guide
Mainframe pairs and Device Manager Agent
Beginning with version 7.4.0, Replication Manager supports configurations in which mainframe
system pairs are managed by Device Manager Agent. As with open system pairs, the status of a pair
managed through Device Manager Agent is acquired from the Replication Manager Agent instance
on the relevant pair management server. The information that can be acquired is the same as for
open system pairs.
Configurations for mainframe monitoring
As of release 6.3, Replication Manager supports monitoring of IBM environments (z/OS, z/VM,
z/VSE and z/Linux) and non-IBM environments using only Device Manager (without HP StorageWorks
P9000 for Business Continuity Manager or P9000 mainframe agent installed). Replication Manager
retrieves the status of Cnt Ac-S/Cnt-Ac-A/BC and Cnt Ac-J copy pairs directly from storage systems,
without depending on mainframe host types. The minimum interval of automatic refresh for this
configuration is 30 minutes.
TIP:
The status of FC and XRC copy pairs are not supported at this time.
Configurations for replica management
The following figure depicts a composite configuration where copy pairs and application replicas
are managed. The system components (hosts) are labeled with both the pair management terms
Configuration Guide 25