Skip to main content
NetApp Knowledge Base

What are the common root causes and solutions of NDMP file history backpressure?

  1. Last updated
    Jun 10, 2024
  2. Save as PDF
Views:
95
Visibility:
Public
Votes:
0
Category:
ndmp
Specialty:
dp
Last Updated:
6/10/2024, 3:07:11 PM

Applies to

  • ONTAP 9
  • NDMP

Answer

  1. File history ingestion at the backup application / DMA common causes and solutions:
    • Cause #1: Resource contention on the server or VM hosting the backup application / DMA as seen in general performance statistics from the hosting OS.
      • Solution #1: Add additional resources to the server / VM hosting the DMA or reduce resource contention to allow for faster ingestion and indexing.
    • Cause #2: Poor performance writing to the file history index database.
      • Solution #2:
        • This is typically due to poor performance of the underlying storage or configuration / sizing issues with the DMA software.
        • Ensure the storage hosting the file history index database has adequate performance.
        • If required, contact your DMA vendor for sizing assistance or other tweaks to allow for faster indexing of file history.

  2. NDMP Server communication to the backup application common cause and solution:
    • Cause: The NDMP control connection is using a latent or lossy network path.
    • Solution:
      • Ensure the network path hosting the NDMP control connection has adequate speed and throughput to support the NDMP control connection and file history messages.
      • Check interface statistics for signs of packet loss or other issues.
      • On a NetApp storage controller, the node-shell ifstatcommand can be used to view interface statistics.
      • Finally, ensure the MTU configured in ONTAP and at the backup application is supported through the entire network path.

Additional Information

FAQ: NDMP File history

 

 

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.