Skip to main content
NetApp adopts Microsoft’s Business-to-Customer (B2C) Identity Management
Effective December 3 - NetApp adopts Microsoft’s Business-to-Customer (B2C) identity management to simplify and provide secure access to NetApp resources. For accounts that did not pre-register (prior to Dec 3) access to your NetApp data may take up to 1 hour as your legacy NSS ID is synchronized to the new B2C identity. To learn more, Read the FAQ and Watch the video. Need assistance? Complete this form and select “Registration Issue” as the Feedback Category. 
NetApp Knowledge Base

How to manage Data ONTAP 8.1 AutoSupport subsystem size and time budgets

Last Updated:

Applies to

  • Clustered Data ONTAP 8.2.x/8.3.x
  • ONTAP 9 or higher systems


This article provides the procedure to manage Data ONTAP 8.1 AutoSupport subsystem size and time budgets.

Note: For specific AutoSupport budget guidance on clustered Data ONTAP 8.2.x/8.3.x and ONTAP 9 or higher systems, refer to KB article AutoSupport can truncate on collection or delivery.

  • AutoSupport has real-world time and size constraints. As Data ONTAP grows in functionality, so does the amount of content collected and delivered in AutoSupport messages. Certain mail servers will drop e-mail messages that have exceedingly large attachments (5MB or greater), and some Web servers have file upload size limitations, too. Users expect storage systems to be able to generate AutoSupport data quickly, with minimal impact to their data serving workflows, and with minimal bandwidth requirements. Data ONTAP 8.1 introduces AutoSupport collection and delivery budgets to help alleviate these issues.
  • Starting with Data ONTAP 8.1, the AutoSupport Collection Framework organizes all content by subsystems. AutoSupport enforces time and size limits during collection to prevent  subsystem content (i.e. commands, tables and files) from not allowing other subsystem content to be collected. If a subsystem exceeds its allotted budget, AutoSupport will halt the collection for that subsystem and move the next subsystem.
  • Once the collection is finished, AutoSupport delivery budgets control the maximum size of the resulting AutoSupport compressed payload archive. There are two delivery size limits: one for SMTP and the other for HTTP (S).
  • If the size of an AutoSupport archive exceeds this size limit, some content will be dropped. During delivery, the content gets added to the archive in the order of priority recorded in the manifest, until the limit is reached.




Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support