Migration of a Data ONTAP 7-Mode qtree Snap-vault destination volume fails
Applies to
- ONTAP 9
- ONTAP 8 7-Mode
Issue
When attempting to use a SnapMirror type-TDP relationship to transition a 7-Mode Qtree SnapMirror destination volume or 7-Mode SnapVault secondary volume to clustered Data ONTAP, the SnapMirror initialize fails.
The SnapMirror type-TDP source 7-Mode controller logs the following error:
Sat Jan 1 00:00:00 EST [source_controller:replication.src.err:error]: SnapMirror: source transfer from <source_volume> to <destination_vserver>:<destination_volume>: transfer failed.
In the event logs on the SnapMirror type-TDP destination cluster, the following messages are logged, which are viewable by running the event log show command:
Sat Jan 1 00:00:00 EST +06:00 [wafl.voltrans.qtree.replica:error] Volume <destination_volume> is a qtree replica. It cannot be transitioned to Cluster-Mode.
Sat Jan 1 00:00:00 EST +06:00 [wafl.mount.inconsistent:error] WAFL: Unable to mount volume <destination_volume> due to Invalid fsinfo block. Volume is marked as inconsistent.
Sat Jan 1 00:00:00 EST +06:00 [snapmirror.dst.OnlineErr:error] SnapMirror not able to bring <destination volume> online, CR_INVALID_FSINFO.
Sat Jan 1 00:00:00 EST +06:00 [replication.dst.err:error] SnapMirror: destination transfer from <source_controller>:<source_volume> to <destination_volume>: replication transfer failed to complete.
Sat Jan 1 00:00:00 EST +06:00 [smc.snapmir.init.fail:error] Initialize from source volume '<source_controller>:<source_volume>' to destination volume '<destination_vserver>: <destination_volume>' failed with error 'Transfer failed.'. Relationship UUID '01234567-0000-1111-2222-012345678901'.
Once a SnapMirror initialization fails to complete in this manner, the destination volume cannot be re-used and should be re-created.