Skip to main content

Azure Blob Storage - Soft Delete

Azure blob storage soft delete is a currently a feature in preview. This feature, as the name suggests, allows Azure to soft delete your blobs when you delete your blobs.
The feature is available for existing storage accounts as well as newly ones that are being created. The feature needs to be explicitly turned on new or existing storage account to reap its benefits.

The feature can be turned on by navigating to the "Blob Service" --> "Soft delete" section of your storage account. The maximum retention policy of these deleted blobs is currently limited to 1 year, the minimum being 1 day. You can configure any value between that. The setting can only be set at the storage account level and is applicable to all the containers within it.

 You can also turn this on using the .Net Azure Storage client. The example below, sets the number of retention days to 2.
 CloudBlobClient client = GetStorageClient();  
 ServiceProperties prop =  
    new ServiceProperties(deleteRetentionPolicy:  
       new DeleteRetentionPolicy { Enabled = true, RetentionDays = 2 });  
 await client.SetServicePropertiesAsync(prop);

When a blob is deleted, the blob is marked as "soft deleted" and is not visible, unless you explicitly list soft deleted blobs .
  foreach (var blob in container  
           .ListBlobs(blobListingDetails : BlobListingDetails.All))  
 {  
    Console.WriteLine(blob.Uri);  
 }

Soft delete also extends to overwriting blobs. When soft delete is turned on, any existing blob that is overwritten, a snapshot of the blob before the it being overwritten is created automatically, the more you update the blob, more snapshots are created.

The storage client, also exposes a new API "Undelete()" on the blob that would bring back the blob and all its snapshots alive.
  await container  
     .GetBlockBlobReference("blob2")  
     .UndeleteAsync();
As of the time of writing the billing aspect of this feature is based on how snapshots are currently billed.


Comments

Post a Comment

Popular posts from this blog

Hosting WCF services on IIS or Windows Services?

There came one of those questions from the client whether to use II7 hosting or windows service hosting for WCF services. I tried recollecting a few points and thought of writing it down. WCF applications can be hosted in 2 main ways - In a Windows service - On IIS 7 and above When WCF was first released, IIS 6 did not support hosting WCF applications that support Non-HTTP communication like Net.TCP or Net.MSMQ and developers had to rely on hosting these services on Windows Services. With the release of IIS 7, it was possible to deploy these Non-Http based applications also on IIS 7. Following are the benefits of using IIS 7 to host WCF applications Less development effort Hosting on Windows service, mandates the creating of a Windows service installer project on windows service and writing code to instantiate the service, whereas the service could just be hosted on IIS by creating an application on IIS, no further development is needed, just the service implementa...
4 comments
Read more

Finalization, Know What it Costs

This is a post about object finalization in .NET. Finalization is not as inexpensive as we think, it increases the pressure put on GC.All objects that need finalization are moved into a finalizable queue and the actual finalization happens in a separate thread. Because the objects full state may be needed, the object itself and all the object it points to are promoted to the next generation (this is needed so that GC does not clean these objects off in the current round), and these objects are cleaned up only after the following GC. Due to this reason, resources that need to be released should be wrapped in as small a finalizable object as possible, for instance if your class needs a reference to an unmanaged resource, then you should wrap the unmanaged resource in a separate finalizable class and make that a member of your class and furthermore the parent should be a non-finalizable class. This approach will assure that only the wrapped class (class that contains the unmanaged resourc...
1 comment
Read more

The maximum nametable character count quota (16384) has been exceeded

Some of our services were growing and the other day it hit the quote, I could not update the service references, nor was I able to run the WCFTest client. An error is diplayed saying " The maximum nametable character count quota (16384) has been exceeded " The problem was with the mex endpoint, where the XML that was sent was too much for the client to handle, this can be fixed by do the following. Just paste the lines below within the configuration section of the devenve.exe.config and the svcutil.exe.config files found at the locations C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE , C:\Program Files\Microsoft SDKs\Windows\v6.0A\bin Restart IIS and you are done. The detailed error that you get is the following : Error: Cannot obtain Metadata from net.tcp://localhost:8731/ Services/SecurityManager/mex If this is a Windows (R) Communication Foundation service to which you have access, please check that you have enabled metadata publishing at the specified address. F...
5 comments
Read more