Skip to main content

NetApp_Insight_2020.png 

NetApp Knowledgebase

How does WAFL_check and wafliron interact with Snapmirror destination volumes in Clustered Data ONTAP 8?

Views:
275
Visibility:
Public
Votes:
0
Category:
data-ontap-8
Specialty:
core
Last Updated:

Applies to

  • Clustered Data ONTAP 8.2
  • Clustered Data ONTAP 8.1
  • Clustered Data ONTAP 8

Answer

Can WAFL_check or wafliron be run on an aggregate containing Snapmirror destination volumes?

Please see the following KB articles for detailed information on WAFL_check and wafliron.

Note: As of Data ONTAP 8.1, WAFL_check has been removed from the boot menu and is no longer a supported operation. Wafliron and wafliron optional commit are to be used instead.

Load Sharing SnapMirror destination volumes

WAFL_check and wafliron will skip over Load Sharing SnapMirror destination volumes. Example of wafliron's attempt against a Load Sharing Snapmirror destination volume:

Run the commands in diag mode

Node1::>set diag

Node1::*>storage aggregate wafliron start -aggregate ls_aggr_1

WARNING: Aggregate ls_aggr_1 contains 1 Load Sharing SnapMirror destination volume(s). If you want to fix inconsistencies on a Load Sharing SnapMirror destination volume, please delete, recreate and resynchronize from the source. Wafliron will skip Load Sharing SnapMirror destination volume(s). Do you still want to continue? {y|n}:

Example of WAFL_check's attempt against a Load Sharing mirror destination (this will be logged to the EMS log file):

Skipping Clustered replica volume @vserver (mirror type drm)

Data Protection SnapMirror destination volumes

By default, WAFL_check will check a Data Protection SnapMirror destination volume. Wafliron will require the option '-include-mirrors' set to 'true' before it will iron a Data Protection SnapMirror destination volume.

Example of wafliron's attempt against a Data Protection SnapMirror destination volume without the option '-include-mirrors' set to 'true':

Node1::*>storage aggregate wafliron start -aggregate dr_aggr_1

WARNING: Aggregate dr_aggr_1 contains 1 Data Protection SnapMirror destination volume(s). You have chosen to skip wafliron on Data Protection SnapMirror destination volume(s). If you want to fix inconsistencies on a Data Protection SnapMirror destination volume, you must use the option '-includemirrors' set to 'true'. Do you still want to continue? {y|n}:

Example of wafliron's attempt against a Data Protection SnapMirror destination volume with the option '-include-mirrors' set to 'true'.

Node1::*>storage aggregate wafliron start -aggregate dr_aggr_1 -include-mirrors true

WARNING: Aggregate dr_aggr_1 contains 1 Data Protection SnapMirror destination volume(s). You have chosen wafliron to fix inconsistencies by breaking the mirror relationship(s) on the Data Protection SnapMirror destination volume(s). Do you still want to continue? {y|n}: y Initiated wafliron-start on aggregate dr_aggr_1.

Data Protection SnapMirror destination volumes - VLDB and WAFL resync and SnapMirror relationship resync

Notice that after the Data Protection SnapMirror destination volume has been ironed, the SnapMirror relationship will be in a 'Broken-Off" state and VLDB and WAFL will have inconsistent information about the destination SnapMirror volume.

Vreport show, vreport fix, and snapmirror resync will be run to continue using the Snapmirror relationship.

Here are the steps:

Node1::>set diag

Node1::*>debug vreport show -instance

Object type: volume

Object: vserver: dst_vol1

List of attributes: Node Name: Node1

Volume DSID: 1048 MSID:2147484688

UUID: 29ad55c0-5c31-11de-9d1b-123475882448

Aggregate Name: dr_aggr_1

Aggregate UUID: 9k2dc7b0-5c49-11de-acb0-00a5882448f

Vserver UUID: 237328fa-1998-11de-8219-12345882448

AccessType: READ_WRITE

StorageType: REGULAR

StripeType: FLEX_VOL

Reason for difference: Present both in VLDB and WAFL with differences

Duplicate Object Values:

Attributes With Differing Values: Volume Access Type

Values In WAFL: READ_WRITE

Values In VLDB: DP_READ_ONLY

Node1::*>debug vreport fix -type volume -object vserver:dst_vol1

Node1::*>set admin

Node1::>snapmirror resync -destination-path cluster_name://vserver/dst_vol1

Now the destination aggregate will be WAFL consistent and the Snapmirror relationship will be resynced and working normally again

Additional Information

additionalInformation_text