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 as follows.
| Data path interface connecting primary and secondary storage systems | Model | Supported firmware version |
|---|---|---|
| 32-Gbps FC | VSP One B20 | All versions |
| 64-Gbps FC | All versions | |
| 10-Gbps iSCSI | All versions | |
| 25-Gbps Ethernet* | A3-04-21-xx and later | |
| 32-Gbps NVMe-oF | Not supported | |
| 64-Gbps NVMe-oF | Not supported | |
| 100-Gbps NVMe/TCP | Not supported | |
| * A 10GBASE-T SFP can be installed on the 25-Gbps Ethernet channel board, in which case the transfer rate is 10 Gbps. | ||
You cannot create a pair combining an NVMe-oF volume (volume that is defined as a namespace on the NVM subsystem added with an NVM subsystem port) and a Fibre Channel volume or iSCSI volume (volume set with an LU path). See the following table.
| Primary data path | Secondary data path | Supported |
|---|---|---|
| NVMe-oF or NVMe/TCP | NVMe-oF or NVMe/TCP | Yes |
| NVMe-oF or NVMe/TCP | Fibre Channel or iSCSI | No |
| Fibre Channel or iSCSI | NVMe-oF or NVMe/TCP | No |
| Fibre Channel or iSCSI | Fibre Channel or iSCSI | Yes |
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.