Describe the difference between Sync and Async SnapMirror replication.

Prepare for the NetApp Certified Technology Solutions Professional Exam. Utilize multiple-choice quizzes, flashcards, and detailed explanations for each question. Boost your confidence and ace your certification effortlessly!

Multiple Choice

Describe the difference between Sync and Async SnapMirror replication.

Explanation:
The difference lies in how commits are acknowledged and how data is kept in sync between the two sites. In synchronous replication, a write is not considered complete until it is durably committed on both the source and the destination. The destination must receive and persist the data before the operation is acknowledged, so the two ends stay in lockstep. This provides near-zero RPO and consistent recovery, but it adds latency and requires a reliable, high-bandwidth link. In asynchronous replication, the write is acknowledged after it is committed on the source side, and the data is sent to the destination later in the background. The destination may lag behind the source, so there is a window of potential data loss if a failure occurs before replication catches up. This reduces write latency and network strain, making it suited for farther distances or where lower impact on production performance is desired, at the cost of higher RPO.

The difference lies in how commits are acknowledged and how data is kept in sync between the two sites. In synchronous replication, a write is not considered complete until it is durably committed on both the source and the destination. The destination must receive and persist the data before the operation is acknowledged, so the two ends stay in lockstep. This provides near-zero RPO and consistent recovery, but it adds latency and requires a reliable, high-bandwidth link.

In asynchronous replication, the write is acknowledged after it is committed on the source side, and the data is sent to the destination later in the background. The destination may lag behind the source, so there is a window of potential data loss if a failure occurs before replication catches up. This reduces write latency and network strain, making it suited for farther distances or where lower impact on production performance is desired, at the cost of higher RPO.

Subscribe

Get the latest from Passetra

You can unsubscribe at any time. Read our privacy policy