Capacity planning
Prioritize pools by available headroom, observed growth, and forecast confidence.
1.Read the facility view
Open Capacity to see pools ranked by the shortest estimated time to their warning threshold. The summary counts pools projected to reach that threshold within 7 or 14 days. This is runway to your warning threshold, not necessarily to a full pool.
Compare allocated percentage, warning and hard thresholds, 24-hour and 7-day growth, the largest dataset contributor, and confidence. Select a pool row to open the storage system’s Capacity tab for context.
2.Set useful thresholds
A Facility Admin or Organization Admin can change capacity and rapid-growth settings in Settings → Capacity & Risk. Use thresholds that leave time for your facility’s purchase, migration, or archive process. Context Mapping can add project and department labels to help identify growth contributors.
A warning threshold is a planning policy. It is not a universal point at which ZFS performance changes. Hardware, fragmentation, workload, and maintenance all affect behavior.
3.Interpret estimates and gaps
Runway is based on observed history. A sudden ingest, deletion, changed workload, or missing samples can change it substantially. Compare the expected date range and confidence with the underlying trend before scheduling work.
An unavailable estimate or an empty capacity view does not mean unlimited headroom. Check whether the host reports pool capacity, whether collection is fresh, and whether enough history exists. Inspect the host directly if an urgent decision cannot wait.
4.Act and verify
- Confirm the pool and the datasets responsible for recent growth.
- Agree on an archive, expansion, or ingest plan with the storage owner; Pillar does not move or delete media for you.
- Recheck capacity after the change and review capacity-forecast routing in Alerts & integrations.