A storage administrator is performing a planned failover of an asynchronous replication. What option should they select to ensure that all data is available at the destination?

Question

Options

• AFailover with sync on the destination array
• BFailover with sync on the source array
• CFailover on the source array
• DFailover on the destination array

• A
  9% (2)
• B
  70% (16)
• C
  17% (4)
• D
  4% (1)

Explanation

Option B is correct because asynchronous replication always has a lag - the destination is behind the source by some amount of unsynced data. When performing a planned failover with sync on the source array, the system flushes all pending/in-flight writes from the source to the destination before the failover completes, guaranteeing zero data loss and full data availability at the destination.

Why the others are wrong:

• A (sync on the destination): The destination doesn't hold the missing data - only the source does. Syncing from the destination side doesn't solve the replication lag.
• C (failover on source, no sync): Skipping the sync step means any data not yet replicated is abandoned at the moment of cutover, causing data loss equal to the async lag window.
• D (failover on destination, no sync): Same problem as C - no sync means the replication gap becomes permanent data loss, and initiating from the destination without sync is the worst option for data completeness.

Memory tip: Think "Source has it, Source ships it." In a planned failover, you control the source - so you trigger the sync there to drain all remaining data to the destination before the handoff. If sync isn't in the option, data loss is guaranteed.

No community discussion yet for this question.