topic Re: Snapmirror from 8.2.2P1 7-Mode to 9.3P4 failed in ONTAP Discussions

Snapmirror from 8.2.2P1 7-Mode to 9.3P4 failed

Leo_Saa — Wed, 04 Jun 2025 13:03:37 GMT

Hi All,

I want to migrate a volume (vol0) from old 2550 running Ontap 8.2.2P1 7-Mode(filehost) to a new 2650 running Ontap 9.3P4 (cltaoc01)

I created a new volume type DP in th new cluster, then I created a peering in transition mode, then I've set a snapmirror and when I try to initialize it return the "State: unitialized" and the "Last Transfer Error: Transfer failed", the logs are below from both machines.

Besides, I have set the hostname and IP address in the /etc/snapmirror.allow and snapmirror state is on, in the 8.2.2.P1. Both machines have the snapmirror license.

Any clue why this this migration is failing? Thanks,

cltaoc01::> volume create -vserver svm00 -volume vol0 -aggregate aggr00 -size 12.5TB -state online -type DP -security-style unix

cltaoc01::> volume show -vserver svm00
Vserver Volume Aggregate State Type Size Available Used%
--------- ------------ ------------ ---------- ---- ---------- ---------- -----
svm00 svm00_root aggr00 online RW 1GB 971.3MB 5%
svm00 vol0 aggr00 online DP 12.50TB 12.50TB 0%

cltaoc01::> vserver peer transition create -local-vserver svm00 -src-filer-name filehost -local-lifs svm00_cifs_nfs_lif

cltaoc01::> snapmirror create -source-path filehost:vol0 -destination-path svm00:vol0 -vserver svm00 -type TDP

cltaoc01::> snapmirror show
Progress
Source Destination Mirror Relationship Total Last
Path Type Path State Status Progress Healthy Updated
----------- ---- ------------ ------- -------------- --------- ------- --------
filehost:vol0
TDP svm00:vol0 Uninitialized Idle - true -

cltaoc01::> snapmirror initialize -destination-path svm00:vol0

cltaoc01::event log> show

12/3/2018 16:19:48 cltaoc01_1 ERROR smc.snapmir.init.fail: Initialize from source volume 'filehost:vol0' to destination volume 'svm00:vol0' failed with error 'Transfer failed.'. Relationship UUID 'bf18bb7e-f751-11e8-8713-00a098de5342'.
12/3/2018 16:19:48 cltaoc01_1 ERROR replication.dst.err: SnapMirror: destination transfer from filehost:vol0 to vol0(1) : replication transfer failed to complete.

Logs from old machine running 8.2.2P1 7-Mode

# tail -6 snapmirror
slk Mon Dec 3 15:57:06 MST state.softlock.vol0.01885e61.087.svm00:vol0(1) Softlock_delete (Transfer)
src Mon Dec 3 16:19:40 MST filehost:vol0 svm00:vol0(1) Request (1XX.XX.YY.6)
slk Mon Dec 3 16:19:47 MST state.softlock.vol0.01885ee4.088.svm00:vol0(1) Softlock_add (Transfer)
src Mon Dec 3 16:19:48 MST filehost:vol0 svm00:vol0(1) Start
src Mon Dec 3 16:19:48 MST filehost:vol0 svm00:vol0(1) Abort (Transfer failed)
slk Mon Dec 3 16:19:48 MST state.softlock.vol0.01885ee4.088.svm00:vol0(1) Softlock_delete (Transfer)

Re: Snapmirror from 8.2.2P1 7-Mode to 9.3P4 failed

SpindleNinja — Tue, 04 Dec 2018 00:55:51 GMT

There's no snapmirror compatiablity between 8.2 (7 or C) to 9.3.

I would use the 7MTT for the transition.

https://www.netapp.com/us/documentation/7-mode-transition-tool.aspx

(Honestly, Creating TDP relationships manually is a pain honestly, just use with the tool.)

Re: Snapmirror from 8.2.2P1 7-Mode to 9.3P4 failed

aborzenkov — Tue, 04 Dec 2018 07:16:39 GMT

7MTT is using the same TDP SnapMirror under the hood. According to IMT, 7MTT CBT from 8.2.2 to 9.3 is supported which means TDP should also work. This sounds more like some networking issue between systems.

Re: Snapmirror from 8.2.2P1 7-Mode to 9.3P4 failed

Sergey_Osipov — Tue, 04 Dec 2018 11:58:37 GMT

I would start with regular checks

if the ip of destination cluster is allowed for snapmirror operations on a source 7-mode system

if both source and destination are pingable to each direction etc.

Re: Snapmirror from 8.2.2P1 7-Mode to 9.3P4 failed

SpindleNinja — Tue, 04 Dec 2018 13:08:53 GMT

8.2 to 9.3 don't have a compatiablity relationship in type DP as stated first in OPs example.

type TDP will work but.. 7MTT is just simplier.

Re: Snapmirror from 8.2.2P1 7-Mode to 9.3P4 failed

aborzenkov — Tue, 04 Dec 2018 13:55:51 GMT

snapmirror show claims it is TDP ...

Re: Snapmirror from 8.2.2P1 7-Mode to 9.3P4 failed

Leo_Saa — Tue, 04 Dec 2018 15:27:18 GMT

The networking is Ok, both machine are connected to the same switch (actually the same line card in the swithc).

cltaoc01::> network ping -destination filehost -vserver svm00 -lif svm00_cifs_nfs_lif1
filehost is alive

filehost> ping svm00
quarry is alive