Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive

Overview of Lifecycle Management

Updated on 2024-10-24 GMT+08:00

Scenarios

The last modification time of an object determines when the lifecycle rule applied to the object becomes effective to periodically transition or delete the object. The transition action is to automatically change objects that are no longer frequently accessed to a storage class with a lower cost without copying the objects themselves.

Figure 1 OBS object lifecycle management
Table 1 Key actions in OBS object lifecycle management

Action

Scenarios

Objects Managed

Operation Guide

Transitions between storage classes

Periodically transition data that is frequently accessed over a period of time but may not be accessed after that period to the Archive or Deep Archive storage class to reduce storage costs. Such data includes digital media, financial and medical records, long-term database backups, and data retained for regulatory compliance.

Objects in a bucket (including the latest and historical versions of objects when versioning is enabled for the bucket)

Transitioning Objects Using Lifecycle Rules

Periodical deletion of objects

Periodically delete data, such as log files, that needs to be retained for a period of time and can be deleted after that period.

  • Objects in a bucket (including the latest and historical versions of objects when versioning is enabled for the bucket)
  • Fragments
    NOTE:

    In a multipart upload, a file is divided into multiple parts and then uploaded. After all parts are uploaded, you can make an API call to assemble the parts into a complete object. The parts that failed to be uploaded or assembled are called fragments. You can continue to execute the interrupted or failed multipart upload to remove fragments, or directly delete fragments to reduce storage costs. For more information about fragments, see Managing Fragments.

  • Expired delete markers
    NOTE:

    An expired delete marker is the only single delete marker that remains after all historical versions of an object are deleted. Removing expired delete markers helps improve performance.

Deleting Objects Using Lifecycle Rules

Points in Time for Lifecycle Management

Below describes the key points in time involved in lifecycle management.

  • An object uploaded to a bucket cannot be modified, so the object's last modification time is when the object was uploaded. Operations, such as changing the object storage class, ACL, metadata, and encryption method and appending data to an object, only change the metadata of an object.
  • For parallel file systems, modifying and truncating a file will change the last modification time of the file.
  • Uploading or copying an object in a bucket or a file in a parallel file system will change their last modification time if there is such an object or a file with the same name. If versioning is not enabled, the last modification time of the object or file is the time when the object or file was last uploaded. If versioning is enabled, a newly uploaded object or file becomes the current version, and the original one becomes a historical version. The last modification time of both the current version and the historical version is the time when the object or file was last uploaded.

After an object is last updated, OBS starts to calculate its lifecycle at the next 00:00 (UTC time). Assume an object was uploaded at 09:00 on June 1, 2024 (UTC). OBS would calculate its lifecycle from 00:00 on June 2, 2024 (UTC). If the object was configured to be deleted one day later, it would be deleted at 00:00 on June 3, 2024 (UTC).

  • It usually takes 24 hours at most for the actions in a lifecycle rule to complete. Considering the start time of the rule, there may be a delay in transitioning storage classes or deleting expired objects, but the total completion time will not exceed 48 hours.

    Assume an object was uploaded at 09:00 on June 1, 2024 (UTC). OBS would calculate its lifecycle from 00:00 on June 2, 2024 (UTC). If the object was configured to be deleted one day later, it would be deleted at 00:00 on June 3, 2024 (UTC). The execution latency does not exceed 24 hours and the deletion would be completed at 00:00 on June 4, 2024 (UTC).

  • If you make changes to an existing lifecycle rule, the lifecycle task on the current day will be terminated and the lifecycle execution time may be prolonged. Therefore, do not frequently change a lifecycle rule. For example, if an object was uploaded at 20:20 on June 1, 2024 (UTC) and has a rule configured to delete it one day later, the rule would be deleted at 00:00 on June 4, 2024 (UTC). However, if the lifecycle rule was modified, for example, the rule name was changed, the lifecycle rule needs to be reloaded and executed again, the deletion may be complete later than 00:00 on June 4, 2024 (UTC).
  • An object uploaded to a bucket cannot be modified, so the object's last modification time is when the object was uploaded. Operations, such as changing the object storage class, ACL, metadata, and encryption method and appending data to an object, only change the metadata of an object.
  • For parallel file systems, modifying and truncating a file will change the last modification time of the file.
  • Uploading or copying an object in a bucket or a file in a parallel file system will change their last modification time if there is such an object or a file with the same name. If versioning is not enabled, the last modification time of the object or file is the time when the object or file was last uploaded. If versioning is enabled, a newly uploaded object or file becomes the current version, and the original one becomes a historical version. The last modification time of both the current version and the historical version is the time when the object or file was last uploaded.

After an object is last updated, OBS starts to calculate its lifecycle at the next 00:00 (UTC time). Assume an object was uploaded at 09:00 on June 1, 2024 (UTC). OBS would calculate its lifecycle from 00:00 on June 2, 2024 (UTC). If the object was configured to be deleted one day later, it would be deleted at 00:00 on June 3, 2024 (UTC).

  • It usually takes 24 hours at most for the actions in a lifecycle rule to complete. Considering the start time of the rule, there may be a delay in transitioning storage classes or deleting expired objects, but the total completion time will not exceed 48 hours.

    Assume an object was uploaded at 09:00 on June 1, 2024 (UTC). OBS would calculate its lifecycle from 00:00 on June 2, 2024 (UTC). If the object was configured to be deleted one day later, it would be deleted at 00:00 on June 3, 2024 (UTC). The execution latency does not exceed 24 hours and the deletion would be completed at 00:00 on June 4, 2024 (UTC).

  • If you make changes to an existing lifecycle rule, the lifecycle task on the current day will be terminated and the lifecycle execution time may be prolonged. Therefore, do not frequently change a lifecycle rule. For example, if an object was uploaded at 20:20 on June 1, 2024 (UTC) and has a rule configured to delete it one day later, the rule would be deleted at 00:00 on June 4, 2024 (UTC). However, if the lifecycle rule was modified, for example, the rule name was changed, the lifecycle rule needs to be reloaded and executed again, the deletion may be complete later than 00:00 on June 4, 2024 (UTC).

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback