Skip to main content
NetApp Knowledge Base

After upgrading to ONTAP 9.4 (or later,) attempts to modify a volume's vserver-dr-protection property fail with "entry doesn't exist."

Last Updated:

Applies to

  • ONTAP 9.4 - ONTAP 9.7
  • One or more DP relationships being converted to SVM DR relationships
  • Some source volumes do not need to be replicated for DR, and are being excluded.


  • When converting Volume Replication relationships (DP relationships) to SVM DR relationships, it is necessary to modify un-needed volumes, setting them as unprotected.
  • If the un-needed volumes are not set as unprotected, the snapmirror resync required for converting to SVM DR will fail.
  • To mark un-needed volumes as unprotected, we use the vol modify command. 
  • After upgrading to ONTAP 9.4, when vol modify is used to set a volume's vserver-dr-protection property to unprotected, the command fails with the message:

Error: command failed: Failed to modify the protection type of the volume [volume name.] Reason: entry doesn't exist. 



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.