Skip to main content
NetApp Knowledge Base

SVMDR Fails with Failed to apply the source Vserver configuration

Views:
118
Visibility:
Public
Votes:
0
Category:
snapmirror
Specialty:
dp
Last Updated:

Applies to

  • ONTAP 9.16.1P4
  • SnapMirror SVM Disaster Recovery (SVMDR)
  • FlexGroup Volumes

Issue

SVMDR replication fails with errors similar to:

LastTransferError: Failed to apply the source Vserver configuration. Reason: Apply failed for Object: volume Method: baseline. Reason: Unable to set volume attribute "space-nearly-full-threshold-percent" for volume "FG_vol__0013" on Vserver "SVMDR_Name". Reason: Volume 'FG_vol__0013' is fenced.

or

Failed to get volume attributes for SVMDR_Name:FG_vol. (Device busy)

Additional symptoms may include:

  • 'volume show 'and' snapmirror show' commands indicate the volume is busy or not present
  • FlexGroup constituent volumes are stuck in a “busy” or “fenced” state
  • Attempts to delete or offline the volume may fail with “Volume busy”
  • Replication relationship status is Idle or Broken-off, but not healthy
  • 'debug vreport show' reports discrepancies between VLDB and WAFL for affected volumes

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.