delete immutability storage account

Justin Huntington 46 Reputation points
2023-07-25T14:08:05.2833333+00:00

I uploaded data to a storage account using Veeam B&R. When i setup the storage account i accidentally set the storage type to RA_GRS instead of LRS.

I left data backing up over weekend now its up to 2.6Tb. I noticed the forecast had sky rocketed so i checked my configuration and changed the storage type to LRS immediately. i also removed the repository from my Veeam B&R to prevent any further activity on the storage account.

It would appear although the storage is immutable it has a lease status of ‘unlocked’, immutability policy retention of ‘0’ and immutability policy state = deleted. So am hoping the blobs / storage account can be deleted to prevent my current forecast becoming a reality.

My storage account has versioning for blobs enabled and when i attempt to disable it I cannot due to VersionLevelWorm being enabled on the storage.

Any assistance would be hugely appreciated.

Thanks

Azure Storage
Azure Storage
Globally unique resources that provide access to data management services and serve as the parent namespace for the services.
3,539 questions
Azure Blob Storage
Azure Blob Storage
An Azure service that stores unstructured data in the cloud as blobs.
3,199 questions
0 comments No comments
{count} votes

Accepted answer
  1. Konstantinos Passadis 19,591 Reputation points MVP
    2023-07-25T14:18:25.9533333+00:00

    Hello @Justin Huntington !

    I understand your issue is with the Storage Account charges because of the blob versioning and Regional Settings

    I would recommend waiting for a while before trying to delete the blobs again. If you still face issues, it would be a good idea to reach out to Azure support.

    Azure Storage billing is based on the amount of data stored in your account, and changing the redundancy option (from RA-GRS to LRS, for example) doesn't immediately affect the stored data or costs. It only changes the redundancy for new data. So, unfortunately, even if you manage to change the redundancy option, you would still have to pay for the data that has already been stored with RA-GRS redundancy.

    You can modify an unlocked time-based retention policy to shorten or lengthen the retention interval. You can also delete an unlocked policy. Editing or deleting an unlocked time-based retention policy for a blob version doesn't affect policies in effect for any other versions. If there's a default time-based retention policy in effect for the container, then the blob version with the modified or deleted policy will no longer inherit from the container.

    have a look please

    https://learn.microsoft.com/en-us/azure/storage/blobs/immutable-storage-overview

    https://learn.microsoft.com/en-us/azure/storage/blobs/immutable-time-based-retention-policy-overview

    https://learn.microsoft.com/en-us/azure/storage/common/redundancy-migration?tabs=portal


    I hope this helps!

    Kindly mark the answer as Accepted and Upvote in case it helped!

    Regards

    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Justin Huntington 46 Reputation points
    2023-07-25T15:04:30.28+00:00

    Thank you kindly for the response Konstantinos.

    Also thanks for the large amount of info.

    My container has an immutability policy state = Deleted, immutability policy retention days = 0 and a lease status = unlocked, legal hold = false.

    However when i look at my policies there are no stored access policies at all or any immutable blob storage access policies in place for me to edit. So was hoping i could remove my blobs or container. But i think this is now prevented by the setting on the storage account itself for 'Enable versioning for blobs'.

    I guess ill have to wait for my retention periods to expire and accept the high forecast bill coming at the end of my billing cycle! :(


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.