Skip to main content
NetApp Knowledge Base

What is NDMP file history back pressure and what impact does it have?

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

Applies to

  • ONTAP 9
  • NDMP

Answer

  • Generating, communicating, and ingesting file history will always add some overhead to a backup.
    • A backup typically always runs faster with file history disabled even if there are no other performance issues.
    • A bottleneck in one step of file history communication can trigger latencies downstream.
  • Due to the way NDMP and dump work together, latency in file history delivery or ingestion can cause a slow-down in the overall backup performance.
    • In other words, dump cannot continue writing data to the backup stream until the associated file history is completely ingested and acknowledged by the backup application / DMA.

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.