Skip to main content
NetApp Knowledge Base

SnapMirror resync or update fails with error "replication operation failed because of error in dense subsystem"

Views:
1,227
Visibility:
Public
Votes:
1
Category:
snaplock
Specialty:
dp
Last Updated:

Applies to

  • Data ONTAP 9.x
  • SnapMirror
  • SVM DR
  • SnapLock

Issue

  • Different types of SnapMirror operations such as (Update, Resync, Initialization, Restore) can fail and may reference dense subsystem
  • SnapMirror resync is failing with the below error:

[Cluster: sm_logger_main: smc.snapmir.resync.fail:error]: Resync from source volume 'SVM1:VOL1' to destination volume 'SVM2:VOL2' failed with error 'Failed to start transfer for Snapshot copy "snapmirror.UUID_SN.Year-MM-DD_TIME".(Failed to start transfer.(Replication operation failed because of error in dense subsystem))'. Relationship UUID 'UUID'.

Tue Sep 26 01:30:34 EDT 2017 ScheduledUpdate[Sep 26 01:12:00]:25335912-a00c-11e7-bfd1-00a098b44571 Operation-Uuid=bbb93bef-42df-4b05-8974-3993aa7ed614 Group=none Operation-Cookie=0 action=Defer source=src_svm:src_vol destination=dr_svm:dr_vol status=Failure message=Failed to start transfer for Snapshot copy "hourly.2017-09-26_0010".(Failed to start transfer.(Replication operation failed because of error in dense subsystem))

  • Or with an error like:
Failed to enable efficiency on volume "VOLUME" of Vserver "VSERVER": Operation is not configured.
Transfer

 

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

Scan to view the article on your device