Hello community, we have the following problem: After a break of SnapVault relationships we get an error message when resync, which is not documented at NetApp. smc.snapmir.resync.fail: resync from source volume 'SRCSVM: SRCVOLNAME' to destination volume 'DSTSVM: DSTVOLNAME' failed with error 'Logical transfer is not allowed to physical mirror volume DSTSVM: DSTVOLNAME.'. Relationship UUID 'SnapVault UUID'. SRC CDOT Cluster 8.2.1 DST CDOT Cluster 8.3.1 Has anyone of you to have an idea and perhaps a solution.
This seems like a mismatch between the two mirror relationships...like one is expecting a DP and the other an XDP relationship type. Is/was the relationship a standard SnapVault, or was it Mirror + Vault (which wasn't introduced until ONTAP 8.3).
If the vault relationship was working as expected previously you may wan to open a support case to have them validate configuration(s) and assist with troubleshooting.
Hope that helps.
If this post resolved your issue, please help others by selecting ACCEPT AS SOLUTION or adding a KUDO.
Hi Andrew, this can not be the cause, because it was a SnapVault relationship between a SVM on a CDOT 8.2.1 Clsuter and SVM on a CDOT 8.3.1 Cluster. We have on the affected volumes a Busy SnapShot begins with snapmirrorSE because the volumes are read only, we can not delete it. The resync with an earlier or later snapshot of the SRC site also does not go. Derr only difference in the volumes is the argument physical-replica, but we believe that this is also not the cause.
YesI'm surethat's ourproblem,we have a fewvolumesasit workedwithoutproblems.Somewe ranintothe problem thatthere is asnapshotofBUSYis onlyhas0Byte.Slowlyusretantion gets out of handandwe have no ideahowwe managetheresync.