Home > Storage > Unity XT > Storage Admin > Dell Unity Dynamic Pools > Traditional pools
After upgrading to a code that supports dynamic pools, traditional pools continue to be supported. However, on all-flash systems, Unisphere no longer allows the creation of a traditional pool in UnityOS version 4.2 and later. For hybrid systems, creating a traditional pool in Unisphere is no longer supported in UnityOS version 5.2 and later. Creating a traditional pool while running these releases requires using the Unisphere CLI or REST API. Viewing, managing, and expanding a traditional pool will continue to be supported using Unisphere, but only the creation option has been removed. When running the Create Pool wizard in Unisphere, a dynamic pool is created.
For ease of reporting and determining pool types, a new property for pools has been added to distinguish between a traditional pool and a dynamic pool. The Type field allows the users to quickly discern between the different pool types. This value is available in the various pool related windows as well as through Unisphere CLI and REST API.
There are a few pool configurations in which the total number of drives required for a configuration is higher in a dynamic pool configuration when compared to a similar configuration created with traditional pools. Specifically, this occurs when multiple pools are created with small drive counts with the same type of drive. For instance, if the solution requires two pools of 15 drives’ worth of capacity each, a single hot spare would be required for traditional pools. For the same capacity, dynamic pools would require a single drive’s worth of spare space per pool, which increases the size of the solution by one drive. In this instance, it may be more cost effective to use traditional pools, though the other benefits of dynamic pools provide would be lost.