Lifecycle Management Overview

Updated on 2022-05-17 GMT+08:00

View PDF

Lifecycle management means periodically deleting objects in a bucket or transitioning between object storage classes by configuring rules.

Figure 1 Lifecycle management

Lifecycle management applies to the following scenarios:

Some periodically uploaded files need only to be retained for one week or one month, and can be deleted once they have expired.
Documents are seldom accessed after a certain period of time. These files need to be transitioned to Warm or Cold storage or be deleted.

You can define lifecycle rules for identifying objects and manage lifecycles of the objects based on the rules.

You can identify what objects in your bucket will be infrequently accessed, and then configure lifecycle rules to transition them to the Warm or Cold storage class to save storage costs. In short, transition basically means that the object storage class is altered without copying the object. You can also manually change the storage class of an object on the Objects page. For details, see Uploading a File.

Lifecycle rules have two key elements:

Configuration policy:
You can also specify the prefix of object names so that objects whose names have this prefix are restricted by the rules. You can configure a lifecycle rule for a bucket so that all objects in the bucket can be restricted by the lifecycle rule.
Time: You can specify the number of days after which objects that have been last updated and meet specified conditions are automatically transitioned to Warm or Cold. Or you can specify an expiration time after which objects are automatically deleted.
- Transition to Warm: You can specify the number of days after which objects that have been last updated and meet specified conditions are automatically transitioned to Warm.
- Transition to Cold: You can specify the number of days after which objects that have been last updated and meet specified conditions are automatically transitioned to Cold.
- Expiration time: You can specify the number of days after which objects are automatically deleted or the day after which an object that matches with a rule is deleted.

The previous number of days for objects to be transitioned to Warm is at least 30. If objects are configured to change to both Warm and Cold, the number of days for transition to Cold must be at least 30 days later than that for transition to Warm. For example, if the number of days for transition to Warm is 33, that for transition to Cold must be 63 at least. If only transition to Cold is enabled and transition to Warm is disabled, there is no limit on the number of days for transition. The expiration time must be greater than the two transition times.

Parent topic: Lifecycle Management

Previous topic: Lifecycle Management

Next topic: Configuring a Lifecycle Rule

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot