The Oracle Cloud Infrastructure (OCI) Object Storage team recently launched a new storage tier called Infrequent Access.
Infrequent Access is a cost-effective storage tier that allows the storing of data that’s accessed infrequently but must be available immediately when needed. This in-between storage tier exists between the Standard and Archive storage tiers. These three tiers of storage are excellent if you know beforehand how often you need to store and access data.
But what if you don’t know what your data access patterns look like? The team at OCI is excited to share the launch of Object Storage Auto-Tiering.
Auto-Tiering lets you let us determine which storage tier your data should be in based on your usage pattern and saves you time from writing complex lifecycle policy rules and deliberating over which storage tier is best for your data. In the end, auto-tiering lets us help you handle the administrative work.
Let’s dive into what’s new with Auto-Tiering and how it can help your storage workflow.
Auto-Tiering for Object Storage is a new feature that helps you automatically move objects between Standard and Infrequent Access tiers based on their access patterns. Set at the bucket level, when you turn on auto-tiering for a bucket, OCI automatically monitors the usage patterns of each object within the bucket.
By turning on Auto-Tiering, you don’t need to write complex object lifecycle management (OLM) policies, understand access patterns of objects, or manually move objects within a bucket. Ultimately, this feature not only reduces overall storage cost, but also saves administration time especially on buckets with many objects.
The Auto-Tiering feature is offered to customers at no cost and applies to all objects greater than 1 MiB. It doesn’t move objects to the Archive tier. To move objects to the Archive tier, read the documentation for Object Lifecycle Management.
The access pattern rules are straightforward and generally work through identifying activity and inactivity for each individual object within a bucket. The most important detail is that if an object hasn’t been read in 31 days, it moves from Standard tier to the Infrequent Access tier. For objects within the Infrequent Access tier, you might encounter data retrieval fees.
Auto-Tiering can’t be enabled if there’s a lifecycle policy rule that already moves objects, object versions, or previous object versions to the Infrequent Access tier.
Auto-Tiering is a great addition to Object Storage’s cost management functionality without having to understand and write complex OLM routines. When turned on in the bucket-level, Object Storage automatically analyzes the access patterns of all objects within a bucket and begins determining the best storage price for each object.
In the end, this feature saves your team in both storage costs and administration time. We hope you enjoy using it!
For more information on related topics, visit the following links: