HP 3PAR Operating System Software - Manual (Page 59)

3. To define the targets for the asynchronous periodic backup system (SystemC) on the primary
system (SystemA), issue the following command on the primary system (SystemA):
•
For RCFC:
# creatercopytarget <target_name> FC <node_WWN> <N:S:P>:<WWN> <N:S:P>:<WWN>
where:
◦
<target_name> —Name of the remote-copy target system (SystemC).
◦
FC —Specifies a FC link.
◦
<node_WWN> —WWN of the target node (node 2FF70002AC0000C3 on SystemC).
◦
<N:S:P>:<WWN> —FC adapter port on the primary system (SystemA), expressed as
node:slot:port, and the WWN of the peer port on the target system (SystemC)
(0:1:1:20210002AC0000C3 and 1:3:2:21210002AC0000C3).
•
For RCIP:
# creatercopytarget <target_name> IP <N:S:P>:<IP_addr> <N:S:P>:<IP_addr>
where:
◦
<target_name> —Name of the remote-copy target system (SystemC).
◦
IP —Specifies an IP link.
◦
<N:S:P>:<IP_addr> —Node on SystemA that contains the IP connections to the
target system, expressed as node:slot:port, and the IP address for the target system
(SystemC) (2:4:1:10.100.33.63 and 3:4:1:10.101.33.63).
Solution Problem
If link performance is below standard, HP 3PAR
Remote Copy does not admit the link. For more
information, see: Before admitting a link to a target definition, HP 3PAR
Remote Copy checks its throughput and latency, which
may be inadequate.
• “Checking RCIP Link Throughput and Latency”
(page 33)
• The event log
Setting Up the Backup Systems for SLD Remote Copy
When you set up the links on the backup storage systems, you create the links in the opposite
direction. Linking three systems to one other creates a second target system for use in the event of
a failover.
1.
To start HP 3PAR Remote Copy on one of the backup storage systems (SystemB), Issue the
following command:
# startrcopy
Setting Up the Backup Systems for SLD Remote Copy 59