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

My CVO aggregate is too large - how can I fix it?

Views:
81
Visibility:
Public
Votes:
0
Category:
cloud-volumes-ontap-cvo
Specialty:
cloud
Last Updated:

Applies to

Cloud Volumes ONTAP (CVO)

Answer

  1. Create a new, smaller aggregate making sure the performance tier of the aggregate is 10% of the capacity tier used.
    • Make sure that the correct tiering policy is assigned:
      • “All” or “Auto” tiering policies should make use of the capacity tier and free up space in the performance tier
      • The default “minimum cooling days” for these policies is high, so you will need to set it to 2 days if you want to see any results sooner

        Understanding FabricPool tiering policies
         
  2. Move the volume

    Considerations and recommendations when moving volumes
     
  3. Delete the old aggregate from Cloud Manager which will also delete the disks in the backend

Additional Information

  • It is not possible to shrink an aggregate.
  • Therefore, if the aggregate is too large for your needs and you would like to use a smaller aggregate and reduce cost, this procedure explains how it can be done.
Scan to view the article on your device