Skip to main content
NetApp Knowledge Base

ONTAP Configuration Backup Fails with configbr.backupFailed.alert

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

Applies to

  • NetApp ONTAP 9
  • AFF-A30 and similar All Flash FAS (AFF) platforms
  • Clusters with configuration backup scratch space set to memory

Issue

  • Scheduled or manual ONTAP configuration backups intermittently fail on one or more nodes.
  • The following alert is observed in EMS logs:
[Node: Node-01: mgwd: configbr.backupFailed:alert]: The node configuration backup Node-01.daily.2026-06-25.00_10_00.7z cannot be created. Error: 'Failed to access file ".tmp.bk.Node-01.daily.13.1782364200" on the root volume'.
  • MGWD logs show the following error:
ERR: config-backup: Unable to reserve enough scratch space to store config backup data. 1024MB was desired, 52MB is the recent max, and only 107MB was available 
  • Backups may succeed at other times, but fail intermittently, especially during periods of high memory utilization

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.