The OCI Object Storage team recently launched a brand 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 is an "in-between" storage tier between the Standard and Archive storage tiers. These three tiers of storage are excellent if you know beforehand how often you will need to store and access data.
However, what if you don't fully know what your data access patterns look like?
This is why 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 or 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 will 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, once you turn on Auto Tiering for a bucket, OCI will automatically start monitoring the usage patterns of each object within the bucket.
By turning on Auto Tiering, you don't need to write complex OLM policies, understand access patterns of objects, or manually move objects within a bucket. Ultimately, this not only reduces overall storage cost, but also saves administration time especially on buckets with many objects.
Auto Tiering is a feature that's offered to customers at no cost, and applies to all objects that are greater than 1 MiB. It does not move objects to Archive tier. In order to move objects to the Archive tier, please read the following documentation for Object Lifecycle Management (OLM).
Auto Tiering can be enabled for any buckets with a Standard default storage tier during creation time using the Console, CLI, and API. Auto Tiering can also be enabled any time after the bucket has been created.
Enabling Auto Tiering for an existing bucket in the Object Storage Console.
The access pattern rules are fairly straightforward, and in general works through identifying activity and inactivity for each individual object within a bucket. The most important detail to note is that if an object has not been read in 31 days, it will be moved from Standard tier to the Infrequent Access tier. As for objects within the Infrequent Access tier, be aware that there may be data retrieval fees.
Note: Auto Tiering cannot be enabled if there is 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. Once turned on in the bucket-level, Object Storage will automatically start analyzing the access patterns of all objects within a bucket, and begin determining the best storage price for each object.
In the end, this saves your team in both storage costs as well as administration time. We hope you enjoy using this feature!
Object Storage, Oracle Cloud Infrastructure