Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 2 results
    • https://kb.netapp.com/on-prem/ontap/Perf/Perf-KBs/CommVault_backups_using_NIC_teaming_in_ONTAP_9.4_and_later_experiencing_low_throughput_over_SMB_3
      Applies to ONTAP 9.4 and later Issue Low throughput seen when backing up data after adding one additional Network Interface Card (NIC), and beginning to use NIC teaming (both NICs as active paths) on ...Applies to ONTAP 9.4 and later Issue Low throughput seen when backing up data after adding one additional Network Interface Card (NIC), and beginning to use NIC teaming (both NICs as active paths) on the CommVault backup machine.
    • https://kb.netapp.com/on-prem/ontap/Perf/Perf-KBs/Deletion_takes_longer_for_large_directories_when_the_SMB_CLOSE_requests_are_runnig_for_longer_duration
      It takes a long time to delete a long directory, the long-running SMB CLOSE requests(WAFL_SPINNP_CLOSE) is the major contributor to the performance drop, and it's caused by the extremely long cpu run ...It takes a long time to delete a long directory, the long-running SMB CLOSE requests(WAFL_SPINNP_CLOSE) is the major contributor to the performance drop, and it's caused by the extremely long cpu run time in WAFL cpu scheduling. High Service Response Time for SMB CLOSE requests in the packet trace Note: The average CPU run time is 1343us, while the Average CPU wait time is 44103us in this example