System requirements and specifications

Control units (CUs)

• Number of CUs: 255
• Range of CUs: 0x00 to 0xfe

  When using the PPRC multi-target function, the range of CUs is 0x00 to 0x7f.

Emulation types

• 3390-3, 3390-9, 3390-L, 3390-M, 3390-A, 3390-V
• When using the PPRC multi-target function, the following emulation types are supported: 3390-1, 3390-2, 3390-3, 3390-9, 3390-L, 3390-M, 3390-A

Supported storage systems

• VSP One Block 85: all versions
• VSP 5000 series: 90-09-29 or later

VSP One B85 (A0-05-41 or later) can be connected to:

• VSP G1x00, VSP F1500^{1, 2}: 80-06-97 or later

Notes:

1. Supports data migration described in Migrating data. The volumes that can be used as data migration source are unpaired (Simplex) volumes of VSP G1x00, VSP F1500 (80-06-97 or later). The volumes that can be used as data migration target are unpaired (Simplex) volumes of VSP One B85 (A0-05-41 or later). Only available for data migration.
2. Supports data migration described in Migrating data using HyperSwap. The following volumes can be used as the data migration source and target:
   • Unpaired (Simplex) volumes
   • ShadowImage for Mainframe P-VOLs (the pair status must be Split, SUSPOP, or Duplex)
   • Compatible FlashCopy^® V2 source volumes

   You can create a ShadowImage for Mainframe pair or a Compatible FlashCopy^® V2 for a TrueCopy for Mainframe pair (S-VOL, the pair status must be Duplex) that is created for data migration. Only available for the Remote FlashCopy function and data migration.

TrueCopy for Mainframe

• Must be installed on the primary and secondary storage systems.
• Separate license codes are required for each storage system.
• TrueCopy can co-exist with TrueCopy for Mainframe.
• A pair with the available licensed capacity exceeded cannot be created.

When using a DP-VOL for the TrueCopy for Mainframe P-VOL or S-VOL:

• If using a DP-VOL for the TrueCopy for Mainframe P-VOL or S-VOL, the capacity of the allocated pages for the DP-VOL will be counted as the licensed capacity of TrueCopy for Mainframe.
• If the actual licensed capacity exceeds the available licensed capacity, the pair creation cannot be performed. In addition, 30 days after the licensed capacity is exceeded, only split or release operations are allowed.

For information about licensed capacity and license expiration, see the System Administrator Guide.

Other required licenses

Remote Replication Extended: Required to use the PPRC multi-target function.

User interfaces

You can use the following UIs to perform TrueCopy for Mainframe operations:

• Command Control Interface (CCI)

  For disaster recovery, CCI must be installed on a host connected to the primary and secondary storage systems.

  A CCI command device is required on the primary and secondary storage systems.

• Business Continuity Manager (BCM)

  A command device is required.

• IBM^® Peer-to-Peer Remote Copy (PPRC) host software functions
• IBM^® DFSMSdss host software functions

Supported host platforms

• z/OS
• z/VM
• z/Linux SUSE
• z/Linux RedHat

For supported versions, refer to the interoperability matrixes at https://compatibility.hitachivantara.com.

Mainframe operations

• Optional error reporting communications (ERC) function requires MVS/DFP 3.2.0 or later.
• If setting a TCz S-VOL as a P-VOL of URz with multiple hosts at primary site and secondary site, a SYSPLEX timer is required to synchronize the time on all hosts.
• ICKDSF R16 + PTF functions require VM/ESA 2.1.0 or later.

Data path

Physical paths connecting the primary and secondary storage systems are required.

Fibre Channel with either direct or switch connections. The following interface is available as a data path:

• Fibre Channel with 32-Gbps link speed* (32-Gbps NVMe-oF, 64-Gbps NVMe-oF, 25-Gbps iSCSI, and 100-Gbps NVMe/TCP are not supported)

  * The 32Gb Fibre Channel Board V2 and 64Gb Fibre Channel Board V2 are not supported.

For details, see Supported data path configurations for Fibre Channel. For details about the supported versions (firmware versions) of the interfaces that can be used as data paths, see Data path requirements and configurations.

Remote paths

• A maximum of 8 remote paths are supported from the primary storage system CU to the secondary storage system CU.
• A primary storage system CU supports a maximum of 32 remote paths (8 paths per secondary storage system CU × 4 supported secondary storage system CUs per primary storage system CU).
• Remote paths are established separately for primary and secondary storage system CUs.
• Fibre Channel, direct, and switch connections are supported.

Maximum number of secondary storage systems (CU)

• A primary storage system CU can be paired with up to 4 secondary storage system CUs.
• A primary storage system can have up to 1,020 paired secondary storage system CUs (255 primary storage system CUs × maximum of 4 secondary storage system CUs).
• Each secondary storage system CU must be added (paired) individually to a primary storage system CU.

Pair volumes

• The S-VOL must be equal-to or larger-than the P-VOL. However,when the S-VOL is larger than the P-VOL, it is not possible to copy data from the S-VOL to P-VOL (for example, swap operation). Therefore, for normal remote copy operations, the PVOL and S-VOL capacity should be equal.
• The maximum capacity of the P-VOL and S-VOL are:
  • DP-VOL: Same as the maximum capacity of a mainframe emulation DP-VOL. For details, see the Provisioning Guide for your storage system.
  • Other than DP-VOL: 262,668 cylinders.
• P-VOLs and S-VOLs can be shared with other Hitachi software product volumes. See Volume types that can be shared with TrueCopy.
• A volume (LDEV) from a parity group with accelerated compression enabled cannot be used directly as a pair volume. Such volumes must be used as pool volumes for an HDP or HDT pool.

Maximum number of pairs

65,280

When BCM or CCI is used, a command device must be defined. In this case, the maximum number of pairs is calculated by subtracting 1 from the above number.

Maximum number of consistency groups

256 (0 to 255) (0x00 to 0xFF)

Disk track format

Error Reporting Communications (ERC) software

For details, see Error reporting communications.