HP XP P9000 Replication Manager Software 7.6.1-00 Configuration Guide

Prerequisites for managing copy pairs using snapshot groups
If a volume is an HP P9500, Replication Manager can manage copy pairs using snapshot groups.
However, the following functions are not available:
Setting alert (pool usage monitoring function for Thin Image is available)
Managing My Copy Groups
Managing replicas
The prerequisites for managing copy pairs using snapshot groups are as follows:
Authentication mode of the command device is enabled.
User authentication for command devices is performed using the raidcom command.
Mainframe pairs and Device Manager Agent
Beginning with v7.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
(example: pair management server) and the replica management counterpart (example: backup
server).
Replication Manager system configurations and requirements28