Expired backups have not immediately freed all capacity
A fictional Avamar service has expired selected backup records under an approved retention change. The physical-capacity report has not dropped by the same amount as the logical data removed from the backup listing. Supplied evidence shows that some content is still referenced by other retained backups and that the relevant maintenance cycle has not finished. A colleague proposes deleting stored segment objects directly to make the graph match the logical total. Another proposes reviewing references, maintenance status, actual unique consumption and the supported capacity process. This exercise executes no expiration, garbage collection or deletion. It asks the learner to explain why logical expiration and physical reclamation differ while protecting the integrity of retained recoverable data.
1. Why is equal immediate reclamation not established?
Read the worked answer
Retained backups can still reference shared content, and maintenance timing affects reclaimable physical space. Logical backup totals are not identical to unique physical consumption.
2. What should the controlled review do?
Read the worked answer
Inspect supported capacity and maintenance evidence, retention/reference relationships and growth. Preserve the valid protection state and follow the approved support process rather than delete underlying segment objects.