Disk Pools - Expanded Functionality

Disk pools are no longer fixed at creation time. You can now evict copies from a physical disk and move empty disks between pools, giving you the flexibility to reconfigure storage mid-life as your needs change. Alongside this, we've improved the experience for adding disks to a pool and made it easier to see where each virtual disk's copies are stored.

Evict copies from a physical disk

Each physical disk now has an Evict Copies action. Evicting moves every virtual disk copy stored on the disk onto other disks in the pool, then disables scheduling so no new copies are placed on it. Use it to empty a disk before repurposing it, or to drain a disk you plan to replace, without disrupting the virtual machines whose copies it holds.

Move disks between pools

Once a disk is disabled and empty, you can move it into a different disk pool, or remove it from its pool entirely. Combined with eviction, this lets you rebalance capacity between pools, retire a pool, or migrate to a new pool layout without rebuilding your storage from scratch. This is particularly useful because a pool's Copy Count is fixed at creation: if you need a different copy count, you can now create a new pool and move your existing disks into it.

Improved disk adding

Adding disks to a pool is now a clearer, guided flow. Select a hypervisor to see its available disks, each listed with its size, vendor, model, and drive type, then stage one or more disks and confirm them in a single step. You can also set a display name for each disk as you add it, making disks easier to identify later.

Copy locations at a glance

Every virtual disk's detail page now shows a Copy Locations table listing each copy alongside the hypervisor and physical disk where it's stored, with links straight to each. When you're planning an eviction or investigating a disk, you can see exactly which copies live where.

These features are available on both Cluster and Standalone deployments. Read more in the Disk Pools documentation.