How do you verify that a SnapMirror relationship is healthy and up-to-date?

How do you verify that a SnapMirror relationship is healthy and up-to-date?

• A. Verify only that the source shows green; service check is enough.
• B. Rely on alert from the source cluster only.
• C. Perform a manual data copy and compare sums.
• D. Check snapmirror status, confirm the baseline transfer completed, monitor transfer history, and validate data integrity on the destination.

Answer: (D)

Ensuring SnapMirror health and currency means looking at four things together: the relationship’s status, that the initial baseline copy is finished, the record of ongoing transfers, and a data integrity check on the destination. The status tells you if the mirror relationship is healthy and whether there are any alarms or lag. Verifying that the baseline transfer completed ensures you started from a complete, correct copy before tracking incremental updates. Monitoring the transfer history shows you that subsequent transfers are happening as expected and helps spot any failures or delays. Finally, validating data integrity on the destination confirms that the data there actually matches the source, not just that copies occurred. When all four pieces look good, you can be confident the SnapMirror relationship is both healthy and up-to-date. Relying only on a green signal from the source, or only on alerts, misses parts of the picture and can hide issues. A manual data copy and sum comparisons isn’t practical for normal operations and doesn’t reflect ongoing replication reliability.

Ensuring SnapMirror health and currency means looking at four things together: the relationship’s status, that the initial baseline copy is finished, the record of ongoing transfers, and a data integrity check on the destination. The status tells you if the mirror relationship is healthy and whether there are any alarms or lag. Verifying that the baseline transfer completed ensures you started from a complete, correct copy before tracking incremental updates. Monitoring the transfer history shows you that subsequent transfers are happening as expected and helps spot any failures or delays. Finally, validating data integrity on the destination confirms that the data there actually matches the source, not just that copies occurred. When all four pieces look good, you can be confident the SnapMirror relationship is both healthy and up-to-date.

Relying only on a green signal from the source, or only on alerts, misses parts of the picture and can hide issues. A manual data copy and sum comparisons isn’t practical for normal operations and doesn’t reflect ongoing replication reliability.