In a VPLEX Metro environment, the write rate on distributed volumes has a direct impact on VPLEX performance with respect to WAN bandwidth. Here’s how:
Distributed Volumes: Distributed volumes in VPLEX Metro span across two geographically separated clusters and are designed to provide continuous availability and data mobility1.
Write Operations: Write operations on distributed volumes require data to be written to both clusters before an acknowledgment is sent back to the host.This ensures data consistency across both sites2.
WAN Bandwidth: The Wide Area Network (WAN) bandwidth between the two clusters is a critical factor in the performance of these write operations.If the WAN bandwidth is insufficient, it can lead to increased latency and reduced throughput3.
Performance Impact: With only half the available WAN-COM paths, VPLEX can exceed bandwidth limitations on the existing WAN-COM paths, causing severe latency impacting the remote writes of distributed devices3.
Best Practices: VPLEX best practices indicate that the round-trip time (RTT) between VPLEX clusters shouldn’t exceed 5 ms to provide the best performance, and an RTT of 1 ms is recommended for a campus-wide network2.
By managing the write rate on distributed volumes and ensuring adequate WAN bandwidth, VPLEX Metro can maintain high performance and meet the required service levels for data availability and accessibility.
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit