You need to review desigh due to complaints from the customer regarding performance of virtual volumes. You make following notes: - Primary DC to Secondary DC = 30 miles and 5 ms roundtrip latency…

Converting all replication jobs to Synchronous Long Distance would still retain the blocking nature of synchronous replication, thus failing to resolve the existing performance problems caused by latency, and potentially worsening them for the DR DC link.

The replication job to the DR DC is already periodic asynchronous, which is appropriate for 15 ms latency and does not cause primary site performance issues; converting it to synchronous would introduce, not resolve, performance problems.

Converting the existing synchronous replication to 'Synchronous Long Distance' still means synchronous operations, which will continue to block primary writes and will not resolve the performance issues caused by the 5 ms latency to the Secondary DC.

Synchronous replication inherently introduces latency to primary site write operations, as it waits for confirmation from the secondary site before acknowledging the write. With 5 ms roundtrip latency, this delay directly impacts virtual volume performance, and converting to periodic asynchronous replication allows primary writes to proceed without waiting for remote acknowledgment, thereby improving performance.