What are the steps in a NetApp DR drill using SnapMirror?

• A. Perform a full data restore from backup.
• B. Test failover only, without validation.
• C. Verify replication is current, perform a test failover/failback, validate data integrity, and update DR runbooks.
• D. Ignore DR runbooks and continue with production.

Answer: (C)

The steps in a NetApp DR drill using SnapMirror center on validating readiness and practicing the full failover process with proper documentation. First, you verify that replication is current. This means checking that the last transfer happened recently and that the data on the DR site is synchronized and consistent with production. If replication isn’t up to date, the DR drill wouldn’t represent a real recovery scenario.

Next, you perform a test failover to the DR site and then a failback. This controlled failover tests whether the DR environment can take over service without disrupting production permanently, and the failback confirms you can return to normal operations after the drill. Running through this sequence helps uncover any gaps in procedures, networking, or access control.

Then you validate data integrity after the failover. This involves ensuring that data volumes, applications, and services are consistent and usable on the DR site, with checks like data checksums, application verifications, and surface-level tests to confirm that recovery meets expectations.

Finally, you update DR runbooks based on what you learned. Document the outcomes, any deviations, timing, and updated steps so future drills are smoother and more accurate.

Other options don’t fit because a drill with SnapMirror isn’t about performing a full data restore from backups as the main step, nor is it acceptable to fail over without validation, and neglecting to update DR runbooks undermines preparedness.