416 IBM Flex System V7000 Storage Node Introduction and Implementation Guide
More details are available at the following address:
http://www-01.ibm.com/support/docview.wss?uid=ssg1S1003634&myns=s033&mynp=famil
yind5329743&mync=E
Additionally, all local zoning rules should be followed. A properly configured SAN fabric is
key to not only local SAN performance, but Remote Copy. You can learn more about these
rules at the following address:
http://publib.boulder.ibm.com/infocenter/storwize/ic/index.jsp?topic=%2Fcom.ibm
.storwize.v7000.doc%2Fsvc_configrulessummary_02171530.html
Remote Copy link requirements
The link requirements are valid for Metro Mirror and Global Mirror. Basically, there are two link
requirements:
Round-trip latency:
The total round-trip latency must be less than 80 ms, and less than 40 ms in each
direction. Latency simulations should be performed with your applications before putting
any network links in place to see if the applications perform at an acceptable level while
meeting the round-trip latency requirement.
Bandwidth:
The bandwidth must satisfy the following requirements:
– If you are not using Change Volumes: Be able to sustain peak write load for all mirrored
volumes and background copy traffic.
– If you are using Change Volumes with Global Mirror: Be able to sustain change rate of
Source Change Volumes and background copy traffic.
– Additional background copy rate (the best practice is 10% to 20% of maximum peak
load) for initial synchronization and resynchronization.
– Remote Copy internal communication at idle with or without Change Volumes is
approximately 2.6 Mbps. This amount is the minimum amount.
Figure 9-67 shows a table of the most common bandwidths available for wide area
network (WAN) line types available in the industry.
Figure 9-67 Wide area network bandwidth speed and feed chart
Fabrics: When a local fabric and a remote fabric are connected together for Remote
Copy purposes, the ISL hop count between a local node and a remote node cannot
exceed seven.
Redundancy: If the link between two sites is configured with redundancy so that it can
tolerate single failures, the link must be sized so that the bandwidth and latency
requirement can be met during single failure conditions.
To Next Page
Loading...
Need help?
General
