What is a recommended step to ensure data freshness after a disaster?

What is a recommended step to ensure data freshness after a disaster?

• A. Perform a final SnapMirror update
• B. Wait for automatic resynchronization
• C. Rebuild caches on all nodes
• D. Recreate exports

Answer: (A)

Ensuring data freshness after a disaster means making sure the DR copy reflects the most recent writes from the primary site. The recommended step is to perform a final SnapMirror update. SnapMirror is NetApp’s replication technology, and running a final update pushes any outstanding changes to the disaster recovery copy so it is synchronized with the latest state before you resume normal operations or perform a failback. This direct action guarantees current data rather than relying on automatic resynchronization, which may lag or take time to complete. Rebuilding caches on all nodes doesn’t change the stored data, only how quickly it can be accessed. Recreating exports affects access paths and permissions, not data accuracy.

Ensuring data freshness after a disaster means making sure the DR copy reflects the most recent writes from the primary site. The recommended step is to perform a final SnapMirror update. SnapMirror is NetApp’s replication technology, and running a final update pushes any outstanding changes to the disaster recovery copy so it is synchronized with the latest state before you resume normal operations or perform a failback. This direct action guarantees current data rather than relying on automatic resynchronization, which may lag or take time to complete. Rebuilding caches on all nodes doesn’t change the stored data, only how quickly it can be accessed. Recreating exports affects access paths and permissions, not data accuracy.