A local ONTAP system has FabricPool configured to a public cloud.

When tiering to the cloud stops in an ONTAP system configured with FabricPool, especially after a rapid increase in storage use, it is likely due to reaching the capacity threshold of the aggregate. ONTAP systems with FabricPool will halt tiering if the aggregate becomes too full. The solution is to adjust the aggregate fullness, either by increasing the aggregate's capacity or by managing the existing data more effectively (e.g., deleting unneeded data or moving data to another aggregate).

Configure tiering to a second cloud provider: This might help in distributing data, but it does not address the issue if the problem is local aggregate capacity.

Increase the tiering license: Generally, tiering licenses are about the amount of data that can be tiered rather than a technical limitation affecting tiering functionality.

Increase the cooling period: This might delay data movement but does not resolve the issue of aggregate fullness halting tiering.

Adjusting the aggregate fullness directly addresses the root cause by ensuring there's sufficient capacity within the local system to continue tiering operations. Information about managing aggregate capacity in ONTAP systems can be found in the ONTAP management documentation or the FabricPool administration guide.