Transitioning Standard Objects to Nearline Storage

What Object Lifecycle Management with SetStorageClass is

Object Lifecycle Management (OLM) in Cloud Storage allows users to define automated rules that manage objects throughout their lifecycle. By using the SetStorageClass action, Cloud Storage automatically transitions matching objects to colder, lower-cost storage tiers (such as Nearline, Coldline, or Archive) without requiring manual scripts or data rewrites.

How it meets the requirements

• Automatic transition after 90 days (✓): Setting the age condition to 90 ensures that Cloud Storage evaluates the object's creation date and triggers the action once the object reaches 90 days of age.
• Targeting existing class (✓): Setting matchesStorageClass to STANDARD ensures the rule only applies to objects currently residing in Standard storage, avoiding unnecessary re-evaluations or redundant operations.
• Destination class (✓): The SetStorageClass action specifies NEARLINE as the target tier, which matches data accessed less than once a month.
• Cost-effective threshold for small files (✓): Setting sizeAboveBytes to 5242880 (5 MiB) establishes a minimum size filter. Small objects beneath this threshold are excluded, preventing the Class A transition operation fee from exceeding the ongoing storage cost savings.

Key advantages and capabilities

• No rewrite penalty: Transitions initiated by SetStorageClass do not rewrite data, avoiding inter-region replication fees and data retrieval charges during transition.
• Cumulative duration tracking: The time spent in the original storage class counts toward the minimum storage duration requirements of the destination storage class.
• Automated asynchronous execution: Cloud Storage inspects bucket contents periodically and executes rules in the background without user intervention.
• Precise filtering: Rules can combine multiple conditions including age, matchesStorageClass, sizeAboveBytes, matchesPrefix, and matchesSuffix to target exact object subsets.

Why this is optimal

This configuration directly targets the specific access pattern by shifting data to the appropriate storage class while safeguarding the organization against uneconomical Class A API transition costs on small files.