HP XP P9000 Command View Advanced Edition Software - Manual (Page 152)

(or exceeds the documented limits), an error occurs during task execution, even if the wizard finishes
normally.
Table 9 Number of generations possible with multi-target configuration
Copy type
Storage system
Snapshot Fast Snap Business Copy
64
64
First layer: 3
Second layer: 2
1
HP P9500
-- XP24000/XP20000
-- XP12000/XP10000/SVS200
Notes:
1. Cascading to second layer is not possible for mainframe pair configurations.
Table 10 Requirement for LUSE volumes when creating a copy pair
Other requirements Maximum number of LUs Storage system
If the primary and secondary
volumes are LUSE volumes, they
must have the same number of
constituent LDEVs.
--
HP P9500
XP24000/XP20000
XP12000/XP10000/SVS200
Prerequisites for pair configuration
The following items need to be verified before performing pair configuration operations.
Open
• The storage system P-VOL and S-VOL are registered to Device Manager and the Device Manager
instance is registered as an information source.
If using a copy type, a remote path is set.
If selecting an LU, it must not be associated with a device group.
• LDEVs that are managed by P9000 RAID Manager and LDEVs that are managed by HP Storage-
Works P9000 for Business Continuity Manager Software do not coexist.
NOTE:
Creating copy pair using LUSE volumes and Fast Snap is not supported
Mainframe
• The disk configuration definition file for the volumes to be used as the P-VOL and S-VOL of the
copy pair has been created using Replication Manager or from a volume scan by HP StorageWorks
P9000 for Business Continuity Manager Software.
• The created disk configuration definition file is stored under the same prefix on the same host.
• Datasets for storing a copy group definition file have been allocated under the same prefix.
• The versions of all instances of BCM registered as information sources in are 6.3 or later.
Managing pair life cycle 152