Skip to main content
NetApp Knowledge Base

CONTAP-809191: Node Configuration Restore Reboots into an Empty Configuration After a File Copy Failure

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

Issue

When a node configuration restore is run with {}system configuration recovery node restore{}, a failure while copying the restored boot device files can go unreported. The restore completes without an error message, and the node reboots with an empty configuration. The node comes back named localhost and starts in the setup wizard, so its prior settings appear to be lost. The only evidence of the failure is a copy error written to the console.

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.