NS0-157 · Question #236
How can you prevent a single SnapMirror relationship from utilizing more than the desired bandwidth?
The correct answer is C. Specify a SnapMirror throttle for that relationship. A per-relationship SnapMirror throttle limits the maximum transfer rate for a single SnapMirror relationship without affecting other relationships or the cluster as a whole.
Question
How can you prevent a single SnapMirror relationship from utilizing more than the desired bandwidth?
Options
- ASpecify a SnapMirror throttle for the destination mode
- BSpecify a SnapMirror throttle for the whole cluster
- CSpecify a SnapMirror throttle for that relationship
- DEnable SnapMirror network compression
How the community answered
(31 responses)- A6% (2)
- B13% (4)
- C77% (24)
- D3% (1)
Why each option
A per-relationship SnapMirror throttle limits the maximum transfer rate for a single SnapMirror relationship without affecting other relationships or the cluster as a whole.
The throttle is applied to the relationship itself, not scoped to the destination node - specifying it only for the destination node is not a valid configuration option.
A cluster-wide throttle would limit all SnapMirror traffic indiscriminately rather than targeting a single relationship.
The 'snapmirror modify -throttle' option applied to a specific relationship sets a kilobytes-per-second ceiling on that individual transfer, giving granular control over bandwidth consumption for that one relationship without impacting others.
SnapMirror network compression reduces the volume of data sent over the wire but does not impose a bandwidth ceiling and therefore cannot guarantee a maximum throughput limit.
Concept tested: SnapMirror per-relationship bandwidth throttle
Source: https://docs.netapp.com/us-en/ontap/data-protection/snapmirror-modify-relationship-task.html
Topics
Community Discussion
No community discussion yet for this question.