Skip to main content
NetApp Knowledge Base

Schedule-besed deduplication does not work after resynchronizing the SVMDR and then breaking the relationship

  1. Last updated
  2. Save as PDF
Views:
16
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
CORE
Last Updated:

Applies to

  • ONTAP 9
  • Deduplication
  • SVM DR

Issue

  • Schedule based deduplication does not work after the following operation :
  1. Configure the SVM DR once and break the relationship. 
  2. Create a same job schedule and efficiency policy on source and destination then enable volume efficiency.  
  3. Resync the SVM DR. 
  4. Break the SVM DR .
  • There is a large number of the following logs on sktrace.log: 

dense_translate_fio_error: Dense failed with error number:[2] code:[23]

  • Same name schedules on exist on jm_sched.xml and a one of a schedule's  owner is Source Cluster and the other one's owner is Destination Cluster. 
  • Deduplication  by volume efficency start  works fine. 

 

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

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.