Shulou(Shulou.com)06/03 Report--

Let's continue to look at some of the more practical features in storage. This time we want to look at the lifecycle management function. This function was launched earlier in Global, and finally landed in mooncake this year. After landing, we began to recommend this feature to users, because it can really bring a lot of benefits to users.

So what exactly can this feature do?

For example, we all know that the cost of blob is relatively low, so we often recommend storing some files in blob to save money, which is a common mode of data storage on the cloud, but for some historical files, such as log files, it is generally very difficult to use them after they have been stored for a period of time. In most cases, we don't need to query the log data from a month or more ago, but we can't delete this kind of data directly, because in the future, there is no guarantee that the data will not be used or meet the requirements of the audit. For this kind of data, what we should do is to archive.

On the cloud, generally speaking, storage is also divided into cold storage and hot storage, and the form of each cloud may be different. AWS S3 can be layered, if archived data can be put in another service glacier, while Azure is uniformly placed in Blob, and there are three layers of cold, hot and archived in Blob. The price of each layer is different, hot data is the most expensive, archived data is the cheapest, and each layer can be converted to each other. Therefore, the best practice for log files like log storage in Azure is to treat them in layers rather than just as hot data, such as converting these log files into cold data after a month or a few months, and finally into archived data after a period of time, which is most suitable for the usage scenario.

In terms of pricing, the pricing of storage tiering is also in line with this scenario, the basic cost of hot storage is the highest, but the cost of reading and writing is relatively low, and the basic cost of archival storage is the lowest, relatively, the cost of reading and writing these data is relatively high.

The setting of specific policies is actually very simple and intuitive.

First, find the storage account for which you want to set the policy, and select add rules here in lifecycle management.

Here you can set how many days the hot storage will be changed to cold storage after the last modification, and how long it will become archive storage.

Finally, the scope for the policy to take effect is also configurable. We can choose a separate container and set the virtual folder in container as the scope for the policy to take effect.

Finally, there are a few points to note

1. Lifecycle policies only apply to block blob,page blob that cannot be used

2.Azure reads the policy once a day, so it may take 24 hours for the policy to take effect, and it may take some time for the specific operation to be completed.

3. If you want to modify storage tier manually, disable the lifecycle policy first

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.