Configure immutability policies for containers that already have data

Question

Planning on configuring immutability policies for azure storage containers which already have data in considerable amounts of TB's. Is there a way to calculate how long it will take? is it best to configure on a storage container with no data before hand?

Answer 1

hi Kwame! thanks for dropping this question ))

yes u can totally set up immutability policies on containers that already have data. microsoft docs confirm it https://learn.microsoft.com/en-us/azure/storage/blobs/immutable-storage-overview. the process itself is instant, no crazy waiting time. but here's the kicker, if u got tons of data (like those TBs u mentioned), the policy applies immediately, but existing blobs might take a bit to fully lock in. no exact ETA, depends on backend processes.

now, about empty containers vs full ones... honestly, it's cleaner to set it up before dumping data in. less weird edge cases, u know? but if u gotta do it retroactively, no sweat, just know u can't tweak retention periods after. once it's set, it's SET.

as well check this, if u use versioning, immutability applies to all versions. https://learn.microsoft.com/en-us/azure/storage/blobs/versioning-overview. worth looking into if u deal with frequent updates. Immutability isn't just an azure thing. other cloud providers handle it similarly, so the logic transfers.

Test this on a small container first. see how it behaves, then scale up. saves u from 'oh no' moments later )) aha, and dont forget, u need 'storage blob data owner' role to set these policies https://learn.microsoft.com/en-us/azure/role-based-access-control/built-in-roles#storage-blob-data-owner

let me know if u hit snags,

rgds,

Alex

Answer 2

Hello , Welcome to MS Q&A

When configuring immutability policies for Azure storage containers, especially those with existing data, there are a few considerations to keep in mind:

Migration Time: Migrating an existing container to support version-level immutability may take some time, and this process cannot be reversed. The exact time it takes can vary based on the amount of data and the current configuration of the container.

Existing Data: If a container already contains data, you must ensure that a container-level time-based retention policy is configured before migrating to support version-level immutability. The migration will fail if this policy is not in place.

Configuration on Empty Containers: Configuring immutability policies on a new, empty container can be more straightforward, as it avoids the complexities of migrating existing data and policies.

Asynchronous Operations: When migrating a container, it's recommended to run the operation asynchronously, as it may take some time to complete. You can check the status of the migration operation to monitor its progress.

For more detailed steps and considerations, you can refer to the Azure documentation on configuring immutability policies.

Kindly accept answers if it helps

Thanks
Deepanshu