What is NDMP file history back pressure and what impact does it have?
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.
- In other words,
Additional Information