Controlling the speed of mirror verification

What mirror verification is

You use mirror verification to ensure that the two plexes of a synchronous mirrored volume are identical. See the synchronous mirror volume management chapter in the Data Protection Guide for more information.

Modifying mirror verification speed

To modify the speed of mirror verification, complete the following step.

Step	Action
1	Enter the following command: options raid.verify.perf_impact impact impact can be high, medium, or low. High means that the filer uses most of the CPU time available for mirror verification; this setting can heavily affect filer performance. Low means that the filer uses very little CPU time; this setting lightly affects filer performance. The default speed is low.

Step

Action

Enter the following command:

options raid.verify.perf_impact impact

impact can be high, medium, or low. High means that the filer uses most of the CPU time available for mirror verification; this setting can heavily affect filer performance. Low means that the filer uses very little CPU time; this setting lightly affects filer performance. The default speed is low.

RAID operations affecting mirror verification speed

When mirror verification and disk scrubbing are running at the same time, Data ONTAP limits the combined resource utilization to the greatest impact set by either operation. For example, if raid.verify.perf_impact is set to medium and raid.scrub.perf_impact is set to low, the resource utilization of both operations has a medium impact.