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

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...

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...

Task based Asynchronous pattern, Async & Await and .NET 4.5

One of the key features in .Net 4.5 is to write asynchronous programs much easier. So if I was to write asynchronous programs in .Net 2.0/3.5, I would either follow the event based model or the callback based model. For an example, a synchronous method that does intensive work (say the DoWork()) can be made asynchronous by using the following patterns 1) Implementing the IAsyncResult pattern. in this implementation, 2 methods are exposed for the DoWork() synchronous method, the BeginDoWork() and the EndDoWork() method. The user will call the BeingDoWork() passing in the required parameters and a callback of the delegate type AsyncCallback(IAsyncResult). The BeginDoWork() will spawn a new thread a return control back to the user. Once work is completed in the spawned method, as a last step, it will call the inform the AsyncResult implementation, which in turns will call the EndDoWork() (which is the callback that was passed in to the BeginDoWork()). 2) Implementing the event pattern. ...