Skip to main content
NetApp Knowledge Base

DR Configuration replication error due to maximum volume count reached for SVM

  1. Last updated
  2. Save as PDF
Views:
55
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
metrocluster
Last Updated:

Applies to

  • ONTAP 9
  • MetroCluster
  • DR Config Replication failed Autosupport

Issue

  • Newly created volumes are not properly replicated to the destination SVM (-mc) in a MetroCluster
  • DR Config Replication failed alert reported due to maximum volume count reached for an SVM 

::*> metrocluster vserver show -fields failed-reason

Apply failed for Object: volume Method: baseline. Reason: Cannot create volume. Reason: Maximum volume count for Vserver svm1-mc reached.  Maximum volume count is 250.

  • Recovery queue shows volumes deleted, which are present after the retention time has expired:

::> volume recovery-queue show -vserver svm1-mc

 

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.