Which scenario is NOT a recommended practice for maintaining data integrity during SnapMirror replication?

• A. Verify integrity on the destination.
• B. Rely solely on source snapshots.
• C. Use snapshot-based replication.
• D. Ensure proper scheduling.

Answer: (B)

Keeping data integrity during SnapMirror replication hinges on validating the destination, using point-in-time snapshots for consistent transfers, and scheduling replication so changes are propagated regularly and predictably. Relying solely on source snapshots isn’t enough because snapshots capture data at one moment on the source and don’t guarantee that the destination has received or remains in sync with all subsequent changes. If a transfer encounters a hiccup or if the source continues changing after the snapshot, the destination can diverge.

Verifying integrity on the destination provides end-to-end assurance that what is stored there truly matches the source, detecting any transmission errors or corruption that occurred during replication. Snapshot-based replication ensures you work with consistent, crash- or application-consistent copies, reducing the risk of transferring an in-progress or inconsistent state. Proper scheduling makes sure replication happens frequently enough to meet recovery objectives and minimizes the window where data could be lost or out of sync.

So, the scenario that isn’t recommended is relying solely on source snapshots, because it does not provide the ongoing validation and synchronization guarantees that the other practices offer.