Skip to main content
NetApp Knowledge Base

What are performance archives and how are they triggered?

Last Updated:

Applies to



  • Performance content is collected and stored (archived) on each system
    • Metrics like node and volume performance statistics are logged
    • Data is kept on the root volume for a rolling 28 days
    • Data is constantly logged, so there is no starting or stopping advanced logging
    • There is minimal overhead to keep latency down
  • Using the AutoSupport(tm) infrastructure, a Performance Archive can be created and uploaded to NetApp
  • Performance archives do not replace performance monitoring or help with sizing as they are intended to troubleshoot ONTAP performance issues
How to upload a Performance Archive?
  1. Confirm the AutoSupport transport is HTTP or HTTPS
    • Cluster::> autosupport show -fields transport
      node            transport
      --------------- ---------
      node1           https
    • Performance archives are typically 50 MB or bigger when compressed so ONTAP is hard coded to not transmit if transport is SMTP
    • If the transport is SMTP, use the manual method with 7zip files or use OneCollect to gather the data
  1. Run the system node autosupport invoke-performance-archive command
    • Cluster::> system node autosupport invoke-performance-archive -start-date "11/31/2022 06:00:00" -duration 4h -case-number 2008123456 -node *
    • Here are the following options for the command:
      • -start-date <"MM/DD/YYYY HH:MM:SS">
      • -duration <[ h][ m][ s]> (or -end-date)
      • -node *
      • -case-number
    • Notes:
  • It is important to note that the maximum duration for any single collection is 6 hours and the recommended sample period is 4 hours
    • Anything less than 2 hours will miss some hourly counters
    • The -start-date must be at least the specified -duration hours in the past, otherwise complete time-frame will not be collected.
    • No error message will be displayed indicating that complete -duration was not collected
  • It is best to start on the top of the hour and end on the top of the hour to capture the hourly counters
    • The whole cluster must be triggered since workload statistics are measured across the cluster
    • Ideally getting the hour before and after the performance event is recommended
    • Date format is recommended to be quotes
  1. To view the progress of the Performance Archive upload you can use the following commands:

::> autosupport history show-upload-details -node <node name> -seq-num <seq-num>

  • The performance archive will show up on Active IQ for the node on the AutoSupport page
  • Once the performance archive is uploaded and appears on Active IQ, then it will be available after a period of time for Support to review
What if performance archive doesn't work?

verify field:
Is the Performance Archive Enabled?: true

if false, enable it by running the following command
::*> statistics archive config modify -is-enabled true

Note: EMS events will also report the following message when the Performance Archive is disabled
::*> event log show  -event perf*
Time                Node             Severity      Event
------------------- ---------------- ------------- ---------------------------
INFORMATIONAL Performance archiver is not enabled.

Why would perfstat be needed?
  • Support will request a perfstat
  • On ONTAP releases up to 9.5, some data may be missing and Support will ask for a perfsat
  • Only gather if requested by Support
  • Sometimes the sales team may request to gather performance data for sizing
How can a storage administrator look at the content within a performance archive?

Additional Information



Scan to view the article on your device