Skip to main content
Question

HSX went read only state

  • April 8, 2026
  • 1 reply
  • 9 views

Good day to all

In my environment HSX went ready mode due to reached 85% threshold i have changed the retention policy from 30 days 1 cycle to 30 days 0 after that i overserved DDB is 0% previously it was 33%  also space is not reclaimed post reclaim and data aging jobs. Kindly suggest

Regards

Robert

1 reply

Bronco
Vaulter
Forum|alt.badge.img+3
  • Vaulter
  • April 8, 2026

Good day to all

In my environment HSX went ready mode due to reached 85% threshold i have changed the retention policy from 30 days 1 cycle to 30 days 0 after that i overserved DDB is 0% previously it was 33%  also space is not reclaimed post reclaim and data aging jobs. Kindly suggest

Regards

Robert

Hello Robert,

 

Based on the screenshots and details provided, the HSX cluster entered ready mode after reaching 85% utilization, following which the retention policy was changed from 30 days/1 cycle to 30 days/0 cycles. However, DDB deduplication savings dropped from 33% to 0%, and no space was reclaimed even after running data aging and reclaim jobs. 

[2] This behavior may occur when Enable Managed Disk Space is enabled, which prevents data aging until the upper watermark is reached. It is recommended to disable this setting and rerun the Data Aging job to allow pruning based on retention policies.

[2] Verify that Data Aging completed successfully, check pending prunable records and pending deletes, and review SIDBEngine.log and SIDBPrune.log for any pruning failures or stalled operations.

[3] Run the Data Retention Forecast and Compliance Report to identify jobs that are not aging due to retention dependencies, extended retention, or interlinked storage policies.

[4] If pruning is complete and space is still not reclaimed, perform Hyperscale space reclamation, confirm that DDB partitions are online and active, and if the issue persists, collect logs and engage Commvault Support for further analysis.

Regards,

Bronco