Skip to main content
NetApp Knowledge Base

Clone-based backup fails, indicating maximum number of volumes reached

  1. Last updated
    Feb 14, 2025
  2. Save as PDF
Views:
82
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:
2/14/2025, 8:56:25 PM

Applies to

  • ONTAP 9
  • Backup applications utilizing clones for backup and restore operations

Issue

  • A clone-based backup, (e.g. a CommVault IntelliSnap backup,) fails with messages similar to:
 
Failed to create clone
Unable to clone from snap
Maximum number of volumes reached on node
 

Error Code: [32.392]
Description: Failed to create clone. :[Error: Unable to clone from snap:[xx_x_xxxxxxxx_xxxxxx_xxxxxxxxxx] of volume:[xxxxxx] on file server:[xxxxxxxxx].Error[Failed to clone volume. FileServer:[xxxxxxxxx] Volume:[/xxxxxxxxx/xxxxxx] SnapName:[xx_x_xxxxxxxx_xxxxxx_xxxxxxxxxx]. Error returned:[13114][Failed to create the clone volume. reason: Maximum number of volumes reached on node 'xxxxx-xxxx-xx"..]]]
Source: xxxxxxxxxxxx-x, Process: FileScan

  • When checking the number of volumes hosted by the NetApp cluster node, the volume count is below the maximum volume threshold.

 

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.