Remote Copy over IP (RCIP) network transport requirements

For RCIP configurations, each link between a pair of storage systems is a logical link between a controller node on one storage system and a controller node on the other storage system in the configuration. These links use a network adapter (NIC) port from each of the nodes in the storage systems.

To use an IP network for Remote Copy, the following requirements must be met.

  • A minimum of two links (a node pair) for each storage system in the Remote Copy configuration.

    Utilizing like node pairs (node pair: 0/1 or 2/3) on each storage system is recommended, but is not a requirement.

  • The NIC interface and the management Ethernet port of the HPE 3PAR StoreServ Storage system controller node must be on different IP subnets.

  • A unique IP address is used for each RCIP NIC interface.

  • The Remote Copy subnet can be shared with other I/O traffic, but a guaranteed amount of bandwidth must be dedicated to Remote Copy. The RCIP network must be sized appropriately to replicate the data being generated. Without a guaranteed amount of bandwidth being dedicated to RCIP, the designated RPO for the solution cannot be guaranteed.

    When replicating synchronously over RCIP, the bandwidth must be large enough to ensure that no performance issues arise from replicating data synchronously. For asynchronous periodic or asynchronous streaming replication, the bandwidth must be large enough to ensure that the RPO can be met.

More information

  • HPE 3PAR StoreServ 3PAR OS 3.3.1 Support Matrix

  • Disaster-tolerant solutions with HPE 3PAR Remote Copy white paper