A data path must be designed to adequately manage all possible amounts of data that could be generated by the host and sent to the P-VOL and S-VOL. The type of interface that can be used for a data path is Fibre Channel or iSCSI (NVMe-oF is not supported). To establish iSCSI connections between the storage systems, make sure to use ports on the 10-Gbps iSCSI channel board. The 25-Gbps iSCSI channel board cannot be used for iSCSI connections between the storage systems. This topic provides requirements and planning considerations for the following key elements of the data path:
- Bandwidth requirements
- Fibre Channel requirements
- Supported data path configurations for Fibre Channel
- iSCSI requirements and cautions
- Ports
Note:
- Create at least two independent data paths (one per cluster) between the primary and secondary systems for hardware redundancy for this critical element.
- When creating more than 4,000 pairs, restrict the number of pairs so that a maximum of 4,000 pairs use one physical path to distribute the loads on the physical paths.
- In a disaster recovery scenario, the same write-workload will be used in the reverse direction. Therefore, when planning TrueCopy for disaster recovery, configure the same number of secondary-to-primary data paths as primary-to-secondary copy paths to maintain normal operations during disaster recovery. Reverse direction paths must be set up independently of the primary-to-secondary paths.
- When you set up secondary-to-primary data paths, specify the same combination of CUs or CU Free and the same path group ID as specified for the primary-to-secondary paths.