5 setting the transport layer, Transport layer considerations, Remote-copy links – HP 3PAR Operating System Software User Manual
Page 26: Rcip, Rcfc
5 Setting the Transport Layer
“Transport Layer Considerations” (page 26)
Review transport layer requirements.
Set the transport layer.
• “Setting Up Remote Copy over IP” (page 27)
• “Setting Up Remote Copy over Fibre Channel”
• “Setting Up RCFC over an IP Network” (page 38)
For more information about the CLI commands in this chapter, see:
•
“About the Remote-Copy Commands” (page 261)
•
HP 3PAR Command Line Interface Reference
Transport Layer Considerations
RCIP
For RCIP, each storage system in the remote-copy configuration should have:
•
At least two nodes with HP-supported GigE PCI adapters.
•
Up to a maximum of one adapter per node.
•
Up to a maximum of eight adapters per system. At least two adapters are required for each
storage system in order to support redundant TCP/IP links between systems.
For 1-to-N remote copy, the primary storage system can have four RCIP interfaces (two interfaces
to each of two backup systems).
For RCIP configurations, the management interface cannot be on the same subnet as the RCIP
network. Up to eight RCIP interfaces are possible.
For RCIP, each GigE interface must use a unique IP address.
RCFC
For RCFC, each storage system should have a pair of HBAs installed. The HBA pair is required
for load sharing and fault tolerance. The HBAs in each storage system connect those systems
through FC SAN, using FC cable connections (see
).
Figure 8 Remote-Copy Links
For HP 3PAR OS 3.1.1 and earlier, the pair of HBAs used for RCFC links must be reserved for
exclusive use by HP 3PAR Remote Copy. For HP 3PAR OS 3.1.3 on HP 3PAR StoreServ 7000
26
Setting the Transport Layer