To ensure data integrity during SnapMirror replication, which practices are recommended?

• A. Use snapshot-based replication (SnapMirror), ensure proper scheduling, and verify integrity on the destination.
• B. Only run replication without verification.
• C. Use continuous replication with no scheduling.
• D. Rely on backups only.

Answer: (A)

Ensuring data integrity during SnapMirror replication relies on three things: capturing a consistent point-in-time image, scheduling the replication for predictable timing, and verifying that the destination truly matches the source after transfer. SnapMirror uses snapshot-based replication to take a consistent snapshot on the source, so what gets copied is a stable, well-defined state rather than a jumble of in-flight updates. Scheduling the replication gives you a controlled window for transfers, aligning with your recovery point objectives and avoiding unexpected load. Verifying integrity on the destination confirms that the replicated data matches the source, catching any corruption or transfer errors that could otherwise go unnoticed.

Relying only on running replication without verification risks undetected data corruption. Continuous replication without scheduling can place unpredictable load on systems and still leave you without a formal post-transfer integrity check. Relying on backups alone doesn’t provide validated, ongoing replication and may miss gaps between backup points.