Skip to main content
NetApp Response to Russia-Ukraine Cyber Threat
In response to the recent rise in cyber threat due to the Russian-Ukraine crisis, NetApp is actively monitoring the global security intelligence and updating our cybersecurity measures. We follow U.S. Federal Government guidance and remain on high alert. Customers are encouraged to monitor the Cybersecurity and Infrastructure Security (CISA) website for new information as it develops and remain on high alert.
NetApp Knowledge Base

Aggravating circumstances for the Back-to-Back scenario

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

Applies to

  • ONTAP 9
  • Data ONTAP 8
  • Data ONTAP 7

Answer

  • The incoming workload (continuous or burst) is greater than what the storage appliance is configured to handle (commonly this includes using slower drives for production loads).
  • Inefficiencies in data layout cause excessive internal systems overhead(usually due to unaligned IO in LUNs or VMDK storage objects).
    • If either of the above circumstances exists, they absolutely must be corrected in an effort to alleviate future performance issues with the storage controller.
    • If the issue is due to unaligned IO on LUNs or VMDK storage objects, this should be the initial focus for addressing the possible performance issues.

Note:

  • Back-to-Back CPs are identified by a 'B' or 'b' in the CP Type column of sysstat output, not simply seeing CPs start in the next sample after one completes.
  • If you are experiencing a performance problem with workload, throughput or latency, then please open a case with NetApp Global Support.

Additional Information

additionalInformation_text

 

Scan to view the article on your device