LifeCycle Management: Blobs inside the nested hierarchy levels (subfolders) are not changed from one tier to another tier. Why?

Question

LifeCycle Management: Blobs inside the nested hierarchy levels (subfolders) are not changed from one tier to another tier. Why?

Seenuvasan, Venkatanathan 65

Hi,

Could you please clarify my doubts regarding Lifecycle Management in Azure Storage (general purpose v2)?

The requirement is to change the access tier from HOT to COOL for the blob that the name starting with the letter 'U'.

blob type is block blob. In general, my folder structure would be in the nested hierarchy level like Container/Directory/Directory1/Directory2/blobs.

Note: Directory1 and 2 are not static one. it will be created automatically based on year/month pattern.

I applied the blob prefix rule in life cycle management in the pattern of container/directory/U.

For example, stage/TestAccessTier/U.

Now, Blobs which are under parent directory level (TestAccessTier), are changed to COOL tier successfully. but the same rule is not worked for the nested directory level. I can not define the nested directories sine those are dynamic one.

Is it possible to achieve the expected outcome in lifecycle management ? Please guide me.

Seenuvasan, Venkatanathan 65 Reputation points

2023-09-04T08:25:42.25+00:00

Can anyone help me here ?
Siva Villa 285 Reputation points Microsoft Employee Moderator

2023-09-05T01:42:01.5633333+00:00

Seenuvasan, Venkatanathan

Welcome to Microsoft Q&A Forum. Thank you for posting your query here!
I understand your requirement to implement a life cycle management policy for migrating files from the HOT to COOL tier within the nested hierarchy folder hierarchy. Please allow me for some time as I conduct an analysis of your requirements in my lab environment and will keep you informed of my findings.

Thank you for your understanding.
Seenuvasan, Venkatanathan 65 Reputation points

2023-09-05T07:19:29.83+00:00

Thanks @Siva Villa

I am waiting..
Siva Villa 285 Reputation points Microsoft Employee Moderator

2023-09-06T08:02:22.7033333+00:00

Seenuvasan, Venkatanathan

I was able to repro this scenario on my lab environment and observed the same behavior. The rule is being applied to the main directory, while the data in sub-folders remains unchanged.

I also attempted to use an asterisk (*) as a wildcard character when implementing the policy, but it did not function as expected. As per the below article, the asterisk character * is a valid character in a blob name. If the asterisk character is used in a prefix, then the prefix will match blobs with an asterisk in their names.

https://learn.microsoft.com/en-us/azure/storage/blobs/storage-blob-faq#the-blob-prefix-match-string-didn-t-apply-the-policy-to-the-expected-blobs

The only feasible option appears to be creating a lifecycle management policy individually targeting each folder.

As an alternative, you will need to develop a custom script and incorporate the function app sample method outlined in the article below.

Lifecycle Management, Page Blob, Azure Storage, Blob Storage (microsoft.com)

Accepted answer

0 additional answers

Your answer

Seenuvasan, Venkatanathan 65 Reputation points

2023-09-04T08:25:42.25+00:00

Can anyone help me here ?
Siva Villa 285 Reputation points Microsoft Employee Moderator

2023-09-05T01:42:01.5633333+00:00

Seenuvasan, Venkatanathan

Welcome to Microsoft Q&A Forum. Thank you for posting your query here!
I understand your requirement to implement a life cycle management policy for migrating files from the HOT to COOL tier within the nested hierarchy folder hierarchy. Please allow me for some time as I conduct an analysis of your requirements in my lab environment and will keep you informed of my findings.

Thank you for your understanding.
Seenuvasan, Venkatanathan 65 Reputation points

2023-09-05T07:19:29.83+00:00

Thanks @Siva Villa

I am waiting..
Siva Villa 285 Reputation points Microsoft Employee Moderator

2023-09-06T08:02:22.7033333+00:00

Seenuvasan, Venkatanathan

I was able to repro this scenario on my lab environment and observed the same behavior. The rule is being applied to the main directory, while the data in sub-folders remains unchanged.

I also attempted to use an asterisk (*) as a wildcard character when implementing the policy, but it did not function as expected. As per the below article, the asterisk character * is a valid character in a blob name. If the asterisk character is used in a prefix, then the prefix will match blobs with an asterisk in their names.

https://learn.microsoft.com/en-us/azure/storage/blobs/storage-blob-faq#the-blob-prefix-match-string-didn-t-apply-the-policy-to-the-expected-blobs

The only feasible option appears to be creating a lifecycle management policy individually targeting each folder.

As an alternative, you will need to develop a custom script and incorporate the function app sample method outlined in the article below.

Lifecycle Management, Page Blob, Azure Storage, Blob Storage (microsoft.com)

Answer 1

Thanks for reaching out to Microsoft Q&A.

A prefix match string of container1/sub1/ applies to all blobs in the container named container1 that begin with the string sub1/.
Since, you have directories with different names part of the same container. It seems that the feasible approach would be to create separate lifecycle management policies for each folder/directory. https://learn.microsoft.com/en-us/azure/storage/blobs/storage-blob-faq#the-blob-prefix-match-string-didn-t-apply-the-policy-to-the-expected-blobs
As an alternative, you will need to develop a custom script and incorporate the function app sample method outlined in the article below.

Lifecycle Management, Page Blob, Azure Storage, Blob Storage (microsoft.com)

Please let us know if you have any further queries. I’m happy to assist you further.

Share via

LifeCycle Management: Blobs inside the nested hierarchy levels (subfolders) are not changed from one tier to another tier. Why?

0 additional answers

Your answer