Storage Account Lifecycle Management Configuration

Question

Storage Account Lifecycle Management Configuration

Vinaya Rao 66

Hello,

I did create the following config for LifeCycle Management. Wondering why there are still backup files going back to 2 or days even though I did set to delete after 1 day. Here is the code view:

{

"rules": [

{

"enabled": true,

"name": "DeleteOldBackupFiles",

"type": "Lifecycle",

"definition": {

"actions": {

"baseBlob": {

"delete": {

"daysAfterModificationGreaterThan": 1

}

},

"filters": {

"blobTypes": [

"blockBlob"

]

}

]

}

Here is the List View of Lifecycle Management under the storage account:

[

](https://filestore.community.support.microsoft.com/api/images/74c7abaf-ba50-4764-85e6-4a0a90d5c2fc?upload=true)

Will appreciate your input on this as I am configuring Lifecycle Management for the first time.

Thanks.

Victor

1 answer

Your answer

Answer 1

deherman-MSFT 38,021 Microsoft Employee Moderator

@deherman-MSFT
Hi Victor. Is this an Azure SQL Database or is it a VM running SQL Server? What is the current backup method that is being used? Can you link the article you mentioned? Thanks!

deherman-MSFT 38,021 Reputation points Microsoft Employee Moderator

2023-08-01T19:17:31.24+00:00
@Vinaya Rao

I understand that you have created a lifecycle management policy to delete your sql backup blobs after 1 day. However, you are not seeing the olders blobs being deleted, please correct me if I am missing something.

There are a couple of possible causes for this. I will provide them here and hopefully they resolve your issue.

The platform runs the lifecycle policy once a day. Once you configure a policy, it can take up to 24 hours to go into effect. Once the policy is in effect, it could take up to 24 hours for some actions to run for the first time.

If you enable firewall rules for your storage account, lifecycle management requests may be blocked. You can unblock these requests by providing exceptions for trusted Microsoft services. For more information, see the Exceptions section in Configure firewalls and virtual networks.

The delete action of a lifecycle management policy won't work with any blob in an immutable container. With an immutable policy, objects can be created and read, but not modified or deleted.

Please confirm that the blobs being deleted are of type blockBlob. Your rule currently only applies to this type of blob.

A lifecycle management policy will not delete the current version of a blob until any previous versions or snapshots associated with that blob have been deleted. If blobs in your storage account have previous versions or snapshots, then you must include previous versions and snapshots when you specify a delete action as part of the policy.

You can check for LifecyclePolicyCompleted to see the results of the policy run.

Hope this resolves your issue. Let me know if it doesn't and we can work with you directly to investigate further.

If you still have questions, please let us know in the "comments" and we would be happy to help you. Comment is the fastest way of notifying the experts.

If the answer has been helpful, we appreciate hearing from you and would love to help others who may have the same question. Accepting answers helps increase visibility of this question for other members of the Microsoft Q&A community.

Thank you for helping to improve Microsoft Q&A!
Vinaya Rao 66 Reputation points

2023-08-02T03:41:01.9933333+00:00

Herman,

Thanks for your response. The sql server version in question is SQL2k14 and blob storage is page blob. From one of the articles of Microsoft, I see that Lifecycle Management is not supported for SQL2k16 and below. I guess, I have to Function App instead? Can you please confirm?

Victor

Share via

Storage Account Lifecycle Management Configuration

1 answer

Your answer