Lifecycle Rule Based on Last Accessed Time
Utilize lifecycle rules based on the last access time to automatically monitor data access patterns. Identify cold data and convert it to a different storage class to enable tiered storage of hot and cold data, ultimately lowering storage costs.
Application scenarios
- Photo album or network disk scenarios
For data that has not been accessed for an extended time, you can set custom dump days to automatically convert cold data to an infrequent access type while still ensuring real-time data availability.
- Life sciences scenario
For large volumes of business data generated through gene sequencing, the classification of data as hot or cold is often determined by the last access time rather than the last modified time. Traditionally, customers managed tiered hot and cold data manually through log analysis or other processes. With lifecycle rules based on the last access time, servers can automatically classify data as hot or cold and implement tiered storage accordingly.
Usage restrictions
- Only buckets without versioning enabled is supported
- Deletion of files and parts is not supported
- Basic lifecycle rules currently support prefix matching but do not support wildcard matching.
Note
When configuring through SDK or API, note that PutBucketLifecycle follows overwrite semantics. For instance, if a bucket already has a lifecycle rule (Rule01) configured and you want to add a new rule (Rule02) in addition to Rule01, follow these steps:
- Use the GetBucketLifecycle API to fetch the current lifecycle rule configuration, Rule01.
- Add Rule02 on top of Rule01.
- Use the PutBucketLifecycle API to update the lifecycle rules to include both Rule01 and Rule02.
For more notes, refer to Notes on Basic Lifecycle Management.
Type of objects dumped
Lifecycle rules based on the last access time support converting objects from standard storage to infrequent access, cold, or archive storage classes. For more storage class introductions, see Introduction to Storage Classes.