After a disaster, the destination volume is activated but users report they do not see the latest updates. What is the most likely cause?

After a disaster, the destination volume is activated but users report they do not see the latest updates. What is the most likely cause?

• A. FlexCache not warmed
• B. SnapMirror relationship wasn't quiesced
• C. A final SnapMirror update wasn't performed
• D. SVM DR was not enabled

Answer: (C)

After disaster recovery, the destination must be brought fully up to date with the source. The most likely cause is that a final SnapMirror update wasn’t performed, so the destination volume was activated but still reflects the state from the last transfer, not the latest writes. Running a final SnapMirror update (or resync) on the destination pulls in all changes since the last transfer, making the data current for users. The other options don’t explain missing recent updates: warming FlexCache affects performance, not data currency; not quiescing the relationship would raise consistency concerns but isn’t the primary reason for stale data after failover; and SVM DR being disabled would prevent DR operations in the first place, which isn’t the observed scenario.

After disaster recovery, the destination must be brought fully up to date with the source. The most likely cause is that a final SnapMirror update wasn’t performed, so the destination volume was activated but still reflects the state from the last transfer, not the latest writes. Running a final SnapMirror update (or resync) on the destination pulls in all changes since the last transfer, making the data current for users. The other options don’t explain missing recent updates: warming FlexCache affects performance, not data currency; not quiescing the relationship would raise consistency concerns but isn’t the primary reason for stale data after failover; and SVM DR being disabled would prevent DR operations in the first place, which isn’t the observed scenario.