| Copy pair requirements (HRpM) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| return to main contents page | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| return to "Management server" contents page | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Preparing the replication environment | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Before replicating volumes or setting up copy pairs using Replication Manager, it is necessary to prepare the prerequisite environment and apply the latest configuration information to Replication Manager. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Ensure that all of the conditions below are satisfied for open systems: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| · The requirements (microcode and system configuration) for ShadowImage, TrueCopy, global-active device or other required storage system volume replication functions must be satisfied. For details about the requirements and the configuration procedures, see the storage system documentation for the applicable storage system model. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| · The storage systems to which the primary and secondary volumes belong are registered as management targets of Device Manager, and the applicable Device Manager server is registered as a Replication Manager information source. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| · A Device Manager agent is installed on the pair management server, and the environment setup has been completed. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| · CCI is installed on the pair management server and the pair management server recognizes the command device in the target storage system. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| · If the pair management server is equipped with more than one NIC, the Device Manager agent and CCI use the same IP address. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| · The primary and secondary volumes are recognized individually from the hosts. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| · The serial numbers for all storage systems managed by Device Manager are unique. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Copy pair configuration conditions | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| You can use the Pair Configuration Wizard to define a copy pair configuration that satisfies the conditions listed in the following table. If the defined configuration does not satisfy these requirements, an error occurs during task execution, even if the wizard finishes normally. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Requirement | Hitachi AMS/WMS | Hitachi AMS2000 | Hitachi Unified Storage 100 | Hitachi Unified Storage VM | Universal Storage Platform V/VM | Virtual Storage Platform | VSP G1000, G1500, VSP F1500 | VSP Gx00 models or VSP Fx00 models | ||||||||||||||||||||||||||||||||||||||||||||||||||
| The number of generations that can be created when a multi-target configuration is used (for ShadowImage) | 3 generations | 8 generations | 8 generations | First layer: 3
generations Second layer: 2 generations |
First layer: 3 generations Second layer: 2 generations For mainframe pair configurations, only 3 generations can be created on the first layer. Cascading to the second layer is not possible. |
First layer:
3 generations Second layer: 2 generations |
||||||||||||||||||||||||||||||||||||||||||||||||||||
| The number of generations that can be created when a multi-target configuration is used (for Copy-on-Write Snapshot) | 15 generations | 32 generations | 32 generations | - | 64 generations | - | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| The number of generations that can be created when a multi-target configuration is used (forThin Image) | - | - | - | 1,024 generations | - | 1,024 generations | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Requirements for LUSE volumes when creating a copy pair by using them | The LUSE volume must be made up of no more than 16 LUs. | The LUSE volume must be made up of no more than 128 LUs. | The LUSE volume must be made up of no more than 128 LUs. | - | If the primary and secondary volumes are LUSE volumes, the number of LDEVs that make up the LUSE volumes must be the same. | For non-Thin Image, When both primary volume and secondary svolume is LUSE, number of LDEVs which consists of LUSE volumes are the same. For Thin Image, Neither primary volume or secondary volume cannot specify LUSE. |
- | - | ||||||||||||||||||||||||||||||||||||||||||||||||||
| -The
capacity of the individual volumes that make up the LUSE volume must be 1 GB
or more. - If the primary and secondary volumes are LUSE volumes, the number of LDEVs that make up the LUSE volumes must be the same. |
- | - | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Volume Conditions | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| (1) Conditions for primary volumes that can be added (open systems) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The primary volumes that are displayed in the Candidate List pane on the 2. Pair Association page of the Pair Configuration Wizard depend on the copy type and the storage system type. Volumes that satisfy all of the following conditions are displayed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| · Volumes must belong to the same storage system as that displayed in Pair List. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| · When volumes belong to an enterprise-class storage system and the copy type is Copy-on-Write Snapshot or Universal Replicator, the emulation type must be OPEN-V. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| · When volumes belong to the Hitachi AMS/WMS, and the copy type is TrueCopy Async, TrueCopy Extended Distance, or Copy-on-Write Snapshot, the pool must be set in the default controller. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| · When the copy type is Copy-on-Write Snapshot/Thin Image, volumes must not be virtual volumes. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| · Volumes must not be reserved by other workflows. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| · Volumes must be internal volumes to which the external volumes are mapped, and the host I/O suppression mode must be disabled. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| · Replication Manager must recognize the command device in the storage system. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| · Multiple volumes that belong to different storage systems must not be selected. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| · The attributes of virtual volumes must not be GAD Reserved. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| (2) Conditions for secondary volumes that can be added (open systems) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The secondary volumes that are displayed the Candidate List pane on the 2. Pair Association page of the Pair Configuration Wizard depend on the copy type and the storage system type. Volumes that satisfy all of the following conditions are displayed in Candidates: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| · The license that is registered in the storage system must be valid. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| · The S-VOL Disable attribute must not be specified. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| · When the copy type is Copy-on-Write/Thin Image, volumes must be virtual volumes. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| · When the copy type is ShadowImage, TrueCopy Async, TrueCopy Extended Distance, TrueCopy Sync, or Universal Replicator, volumes must not be virtual volumes. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| · When volumes belong to an enterprise-class storage system and the copy type is Copy-on-Write Snapshot or Universal Replicator, the emulation type must be OPEN-V. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| · When volumes belong to the Hitachi AMS/WMS, and the copy type is TrueCopy Async or TrueCopy Extended Distance, the pool must be set in the default controller. Also, the default controller must match the current controller. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| · The storage system must satisfy the following conditions: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| · When the copy type is ShadowImage, Copy-on-Write Snapshot/Thin Image, the volume of the storage system must be the same as that of the primary volume. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| · When the copy type is TrueCopy Async, TrueCopy Extended Distance, the volume of the storage system must be different from that of the primary volume. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| When the primary volume belongs to an enterprise-class storage system, the storage system type must be Universal Storage Platform V/VM, Virtual Storage Platform, VSP G1000, G1500, VSP F1500, VSP Gx00 models, VSP Fx00 models, or HUS VM. When the primary volume belongs to a midrange storage system, the storage system type must be the same as that of the primary volume. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| · When the copy type is Universal Replicator, the storage system must be different from that of the primary volume, and the storage system type must be Universal Storage Platform V/VM, Virtual Storage Platform, VSP G1000, G1500, VSP F1500, VSP Gx00 models, VSP Fx00 models, or HUS VM. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| · Volumes must not be command devices or remote command devices. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| · Volumes must not be virtual volumes. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| · Volumes must not be reserved by other workflows. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| · Volumes must be internal volumes to which the external volumes are mapped, and the host I/O suppression mode must be disabled. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| · Replication Manager must recognize the command device in the storage system. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| · Multiple volumes that belong to different storage systems must not be selected. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||