Overview

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

Scenarios

As Internet develops, data storage scenarios become increasingly diverse. Limited storage classes cannot meet diverse storage and cost management requirements. OBS provides the following storage classes: Standard, Infrequent Access, Deep Archive (under a beta test), and Archive. For more information about billing for different storage classes, see Storage Space.

Storage Classes

OBS supports the following storage classes:

Standard
Infrequent Access
Archive
Deep Archive (Under a Beta Test)

Scenarios: The Standard storage class features low latency and high throughput. It is therefore good for storing frequently (multiple times a month) accessed files or small files (less than 1 MB). Its application scenarios include big data analytics, mobile apps, hot videos, and social apps.
Redundancy: The Standard storage class provides two redundancy options. Multi-AZ storage means data is stored in multiple AZs, which enables more reliability. Single-AZ storage means data is stored in a single AZ, which enables more cost-effectiveness.
Specifications: The minimum billable object size is 64 KB. There is no requirement for the minimum storage duration.
NOTE:
- The minimum billable object size refers to the minimum object size that is eligible for billing. For example, a 32 KB Standard object will be billed as if it were 64 KB.
- The minimum storage duration refers to the least time that is eligible for billing. This means that objects will be billed for the minimum storage duration even if they are not stored for that long. For example, if an Infrequent Access object is deleted after being stored in OBS for 20 days, it will be billed for the storage of 30 days (the minimum storage duration).
Data restoration: N/A
NOTE:
- To access objects in the Archive or Deep Archive storage class, including reading or downloading them, accessing them with a URL, or configuring an ACL or metadata for them, you must first restore them. For more information, see Restoring an Object from Archive or Deep Archive Storage.

Scenarios: The Infrequent Access storage class is for storing data that is infrequently (less than 12 times a year) accessed, but when needed, the access has to be fast. It can be used for file synchronization, file sharing, enterprise backups, and many other scenarios.
Redundancy: The Infrequent Access storage class provides two redundancy options. Multi-AZ storage means data is stored in multiple AZs, which enables more reliability. Single-AZ storage means data is stored in a single AZ, which enables more cost-effectiveness.
Specifications: The minimum billable object size is 64 KB. The minimum storage duration is 30 days.
Data restoration: Infrequent Access objects can be accessed only after being restored. The restoration process is automatically completed by the system and users are unaware of the restoration. When accessing Infrequent Access objects, you are charged for requesting and restoring objects. There is no billing for temporary file storage.
NOTE:
- Data restoration charges involve the request charge, restoration charge (standard or expedited), and temporary file storage charge. For details, see Data Restoration Pricing. To calculate an estimated price, use Price Calculator.

Scenarios: The Archive storage class is ideal for storing data that is rarely (once a year) accessed. Its application scenarios include data archiving and long-term backups. This storage class is secure, durable, and inexpensive, so it is often used to replace tape libraries. To keep cost low, it may take up to hours to restore data from the Archive storage class.

Redundancy: The Archive storage class only supports single-AZ redundancy.
Specifications: The minimum billable object size is 64 KB. The minimum storage duration is 90 days.
NOTE:
- The minimum billable object size refers to the minimum object size that is eligible for billing. For example, a 32 KB Standard object will be billed as if it were 64 KB.
- The minimum storage duration refers to the least time that is eligible for billing. This means that objects will be billed for the minimum storage duration even if they are not stored for that long. For example, if an Archive object is deleted after being stored in OBS for 80 days, it will be billed for the storage of 90 days.
Data restoration: Archive objects can be accessed only after being restored. The Archive storage class supports standard and expedited restoration. The standard restoration takes 3 to 5 hours, and the expedited restoration takes 1 to 5 minutes. You can enable Direct Reading to access Archive objects without restoration. Direct reading is billable. Decide whether or not to use this function based on your requirements.
NOTE:
- Data restoration charges involve the request charge, restoration charge (standard or expedited), and temporary file storage charge. For details, see Data Restoration Pricing. To calculate an estimated price, use Price Calculator.

Scenarios: The Deep Archive storage class is suitable for storing data that is barely (once every few years) accessed. This storage class costs less than the Archive storage class, but takes longer time (usually several hours) to restore data.
Redundancy: The Deep Archive storage class only supports single-AZ redundancy.
Specifications: The minimum billable object size is 64 KB. The minimum storage duration is 180 days.
NOTE:
- The minimum billable object size refers to the minimum object size that is eligible for billing. For example, a 32 KB Standard object will be billed as if it were 64 KB.
- The minimum storage duration refers to the least time that is eligible for billing. This means that objects will be billed for the minimum storage duration even if they are not stored for that long. For example, if a Deep Archive object is deleted after being stored in OBS for 170 days, it will be billed for the storage of 180 days.
Data restoration: Deep Archive objects can be accessed only after being restored. The Deep Archive storage class supports standard and expedited restoration. The standard restoration takes 5 to 12 hours, and the expedited restoration takes 3 to 5 hours.
NOTE:
- Data restoration charges involve the request charge, restoration charge (standard or expedited), and temporary file storage charge. For details, see Data Restoration Pricing. To calculate an estimated price, use Price Calculator.

Scenarios: The Standard storage class features low latency and high throughput. It is therefore good for storing frequently (multiple times a month) accessed files or small files (less than 1 MB). Its application scenarios include big data analytics, mobile apps, hot videos, and social apps.
Redundancy: The Standard storage class provides two redundancy options. Multi-AZ storage means data is stored in multiple AZs, which enables more reliability. Single-AZ storage means data is stored in a single AZ, which enables more cost-effectiveness.
Specifications: The minimum billable object size is 64 KB. There is no requirement for the minimum storage duration.
NOTE:
- The minimum billable object size refers to the minimum object size that is eligible for billing. For example, a 32 KB Standard object will be billed as if it were 64 KB.
- The minimum storage duration refers to the least time that is eligible for billing. This means that objects will be billed for the minimum storage duration even if they are not stored for that long. For example, if an Infrequent Access object is deleted after being stored in OBS for 20 days, it will be billed for the storage of 30 days (the minimum storage duration).
Data restoration: N/A
NOTE:
- To access objects in the Archive or Deep Archive storage class, including reading or downloading them, accessing them with a URL, or configuring an ACL or metadata for them, you must first restore them. For more information, see Restoring an Object from Archive or Deep Archive Storage.

Scenarios: The Infrequent Access storage class is for storing data that is infrequently (less than 12 times a year) accessed, but when needed, the access has to be fast. It can be used for file synchronization, file sharing, enterprise backups, and many other scenarios.
Redundancy: The Infrequent Access storage class provides two redundancy options. Multi-AZ storage means data is stored in multiple AZs, which enables more reliability. Single-AZ storage means data is stored in a single AZ, which enables more cost-effectiveness.
Specifications: The minimum billable object size is 64 KB. The minimum storage duration is 30 days.
Data restoration: Infrequent Access objects can be accessed only after being restored. The restoration process is automatically completed by the system and users are unaware of the restoration. When accessing Infrequent Access objects, you are charged for requesting and restoring objects. There is no billing for temporary file storage.
NOTE:
- Data restoration charges involve the request charge, restoration charge (standard or expedited), and temporary file storage charge. For details, see Data Restoration Pricing. To calculate an estimated price, use Price Calculator.

Scenarios: The Archive storage class is ideal for storing data that is rarely (once a year) accessed. Its application scenarios include data archiving and long-term backups. This storage class is secure, durable, and inexpensive, so it is often used to replace tape libraries. To keep cost low, it may take up to hours to restore data from the Archive storage class.

Redundancy: The Archive storage class only supports single-AZ redundancy.
Specifications: The minimum billable object size is 64 KB. The minimum storage duration is 90 days.
NOTE:
- The minimum billable object size refers to the minimum object size that is eligible for billing. For example, a 32 KB Standard object will be billed as if it were 64 KB.
- The minimum storage duration refers to the least time that is eligible for billing. This means that objects will be billed for the minimum storage duration even if they are not stored for that long. For example, if an Archive object is deleted after being stored in OBS for 80 days, it will be billed for the storage of 90 days.
Data restoration: Archive objects can be accessed only after being restored. The Archive storage class supports standard and expedited restoration. The standard restoration takes 3 to 5 hours, and the expedited restoration takes 1 to 5 minutes. You can enable Direct Reading to access Archive objects without restoration. Direct reading is billable. Decide whether or not to use this function based on your requirements.
NOTE:
- Data restoration charges involve the request charge, restoration charge (standard or expedited), and temporary file storage charge. For details, see Data Restoration Pricing. To calculate an estimated price, use Price Calculator.

Scenarios: The Deep Archive storage class is suitable for storing data that is barely (once every few years) accessed. This storage class costs less than the Archive storage class, but takes longer time (usually several hours) to restore data.
Redundancy: The Deep Archive storage class only supports single-AZ redundancy.
Specifications: The minimum billable object size is 64 KB. The minimum storage duration is 180 days.
NOTE:
- The minimum billable object size refers to the minimum object size that is eligible for billing. For example, a 32 KB Standard object will be billed as if it were 64 KB.
- The minimum storage duration refers to the least time that is eligible for billing. This means that objects will be billed for the minimum storage duration even if they are not stored for that long. For example, if a Deep Archive object is deleted after being stored in OBS for 170 days, it will be billed for the storage of 180 days.
Data restoration: Deep Archive objects can be accessed only after being restored. The Deep Archive storage class supports standard and expedited restoration. The standard restoration takes 5 to 12 hours, and the expedited restoration takes 3 to 5 hours.
NOTE:
- Data restoration charges involve the request charge, restoration charge (standard or expedited), and temporary file storage charge. For details, see Data Restoration Pricing. To calculate an estimated price, use Price Calculator.

Comparison of Storage Classes

Item	Standard	Infrequent Access	Archive	Deep Archive (Under Limited Beta Testing)
Feature	Top-notch performance, high reliability and availability	Reliable, inexpensive storage with real-time access	Long-term, inexpensive storage for Archive data	Long-term storage for Deep Archive data, with a lower unit price than Archive storage
Use cases	Cloud applications, data sharing, content sharing, and hot data storage	Web disk applications, enterprise backups, active archiving, and data monitoring	Archiving, medical image storage, video material storage, and replacement of tape libraries	Archive data that is barely accessed
Designed durability (single-AZ)	99.999999999% (11 nines)	99.999999999% (11 nines)	99.999999999% (11 nines)	99.999999999% (11 nines)
Designed durability (multi-AZ)	99.9999999999% (12 nines)	99.9999999999% (12 nines)	Not supported	Not supported
Designed availability (single-AZ)	99.99%	99%	99%	99%
Designed availability (multi-AZ)	99.995%	99.5%	Not supported	Not supported
Minimum billable object size	64 KB	64 KB	64 KB	64 KB
Minimum storage duration	N/A	30 days	90 days	180 days
Data access speed	Real-time access	Real-time access	If direct reading is disabled, objects must be restored before you can access them. Standard restoration: 3–5 hours; Expedited restoration: 1–5 minutes If direct reading is enabled, objects can be accessed in real time.	Objects must be restored before you can access them. Standard restoration: 5–12 hours; Expedited restoration: 3–5 hours
Data restoration charges	N/A	Billed for each GB restored.	Billed for each GB restored. Pricing differs depending on standard or expedited restoration.	Billed for each GB restored. Pricing differs depending on standard or expedited restoration.
Image processing	Supported	Supported	Not supported	Not supported

Parent Topic: Storage Class

Previous topic: Storage Class

Next topic: Configuring a Storage Class

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