Which condition triggers the expansion from 32-bit to 64-bit aggregates in NetApp Data ONTAP?

Which condition triggers the expansion from 32-bit to 64-bit aggregates in NetApp Data ONTAP?

• A. All aggregates are automatically converted from 32-bit to 64-bit with the Data ONTAP 8.1 upgrade
• B. The expansion is triggered by an aggr convert command
• C. The expansion is triggered by adding disks to exceed 16TB
• D. The 32-bit aggregates are degraded and must be Volume Snap Mirrored to a new 64-bit aggregate with Data OnTap 8.1

Answer: (C)

Aggregates using 32-bit addressing are capped at about 16 TB of raw capacity. When you add disks and the aggregate’s size exceeds that 16 TB limit, Data ONTAP automatically switches the addressing to 64-bit, allowing much larger aggregates. So the trigger is crossing the 16 TB boundary due to adding disks. Upgrading or running a manual convert isn’t the trigger itself; automatic expansion happens because you’ve grown beyond the 32-bit limit.

Aggregates using 32-bit addressing are capped at about 16 TB of raw capacity. When you add disks and the aggregate’s size exceeds that 16 TB limit, Data ONTAP automatically switches the addressing to 64-bit, allowing much larger aggregates. So the trigger is crossing the 16 TB boundary due to adding disks. Upgrading or running a manual convert isn’t the trigger itself; automatic expansion happens because you’ve grown beyond the 32-bit limit.