# How do retention rules interact with object versioning?

Canonical URL: https://help.iagenify.com/faqs/object-storage/how-do-retention-rules-interact-with-object-versioning

[← Back to Object Storage FAQs](https://help.iagenify.com/faqs/object-storage)

HELP CENTER · FAQ Object Storage 1 min read
# How do retention rules interact with object versioning?
Retention settings and versioning solve different problems: retention controls how long data is kept, while versioning preserves multiple object states. Their interaction depends on provider policy, so check which versions, delete markers, and legal holds the rule actually covers.
IaGenify
Object Storage

## Identify what the policy retains
Determine whether the configured period applies to the current version only, every version, or objects with a specific tag or prefix. A lifecycle rule may transition or expire versions differently from the visible current object.
With versioning enabled, deleting an object may create a delete marker while earlier versions remain stored and billable. A retention policy can also prevent deletion until its deadline, even if the object no longer appears in ordinary listings.
## Test lifecycle behavior before broad rollout
Use a small test prefix with representative versions and verify transitions, expiration, and delete-marker behavior using the provider's documented controls. Check whether legal holds or retention locks override lifecycle actions.
Estimate storage and retrieval effects across all retained versions, and document the intended recovery window. Do not promise permanent preservation from versioning alone; pair it with explicit retention, access controls, and tested restore procedures. [← Back to Object Storage FAQs](https://help.iagenify.com/faqs/object-storage)