Skip to main content

How to replicate Azure Blobs

In today post we will talk about how we can replicate content in multiple storage accounts of Azure.
If you remember the last post that I had, this one is related to it and describes the replication process.
First of all
Why we need to do something like this?
There are cases when we have a system that is distributed on multiple data centers and we want to be able to have the specific content in all locations around the globe. We don’t want a user from China to requests binary content from Europe if the system is deployed in China also. We could use CDNs but CDNs don’t have support for Shared Access Signature (SAS)
Beside this, if we have a lot of clients that will requests the same blob content than we will have a problem. A blob can handle maximum 500 requests and the bandwidth that is available per blob is around 60MB. This mean that if we have 100 clients, that wants to download the content with 1MB each than... will have a small problem.
When we talk about replication don’t imagine that replication needs to be done on different datacenters. The content can be replicated in the same datacenters on different blobs under the same storage account or using different storage accounts.
Below, we can see a diagram that present a replication schema that is:

  • On two storage accounts in the main datacenters
  • On four other datacenters (one storage account per data centers)


The secret around replication action is ‘StartCopyFromBlobAsync’. This method allow us to trigger a copy action from a blob to another blob. In this way we can easily copy all the content of a blob (including properties, metadata and payload) to another blob without having manually to manage each step.
Once the action is triggered, you will need to check the async operation status and make sure that the copy action finished with success.
await destinationBlob.StartCopyFromBlobAsync(new Uri(sourceBlobUri));

  • The status that is returned by can be:
  • CopyStatus.Aborded – the copy action was aborted
  • CopyStatus.Failed – an error occurred
  • CopyStatus.Pending – copy is still in progress
  • CopyStatus.Success – copy was finished

We don’t have any control at how long the copy action will take. Because of this we need to wait the action to finish and check the status code. As input uri, we can even use a secure blob storage that has a SAS token.
public class BlobReplication
    {       
        public async Task ReplicateBlobAsync(string blobSasUri, CancellationToken cancellationToken = default(CancellationToken))
        {
            List<ICloudBlob> destBlobs = new List<ICloudBlob>();

            try
            {
                var sasUri = new Uri(blobSasUri);

                var blobClient = new CloudBlobClient(sasUri);

                ICloudBlob sourceBlob = blobClient.GetBlobReferenceFromServer(sasUri);

                var startCopyTasks = new List<Task<ICloudBlob>>();

                foreach (var destConnectionString in configuration.ReplicationStorageAccounts.Select(c => c.ConnectionString))
                {                    
                    var destStorageAccount = CloudStorageAccount.Parse(destConnectionString);                    
                    if (destStorageAccount.BlobEndpoint.ToString() != storageAccount.BlobEndpoint.ToString())
                    {
                        var task = StartReplicationAsync(sourceBlob, blobSasUri, destStorageAccount, cancellationToken);
                        startCopyTasks.Add(task);
                    }
                }

                await Task.WhenAll(startCopyTasks);
                destBlobs = startCopyTasks.Select(t => t.Result).ToList();
                
        await WaitForBlobCopy(destBlobs, cancellationToken);
            }
            catch (OperationCanceledException)
            {                
                foreach (var dest in destBlobs)
                {
                    try
                    {
                        var destBlob = dest.Container.GetBlobReferenceFromServer(dest.Name);

                        if (destBlob.CopyState.Status == CopyStatus.Pending)
                        {
                            destBlob.AbortCopy(destBlob.CopyState.CopyId);
                        }

                    }
                    catch (Exception)
                    {
            ...
                    }
                }
                throw;
            }
        }

        private async Task<ICloudBlob> StartReplicationAsync(ICloudBlob sourceBlob, string sourceBlobSasUri, CloudStorageAccount destStorageAccount,
            CancellationToken cancellationToken = default (CancellationToken))
        {
            string containerName = sourceBlob.Container.Name;

            CloudBlobContainer destContainer = await destStorageAccount.GetBlobContainerAsync(containerName);

            ICloudBlob destBlob;    
            if (sourceBlob.Properties.BlobType == BlobType.BlockBlob)
            {
                destBlob = destContainer.GetBlockBlobReference(sourceBlob.Name);
            }
            else
            {
                destBlob = destContainer.GetPageBlobReference(sourceBlob.Name);
            }

            await destBlob.StartCopyFromBlobAsync(new Uri(sourceBlobSasUri), cancellationToken);

            return destBlob;
        }

        private async Task WaitForBlobCopy(List<ICloudBlob> blobs, CancellationToken cancellationToken = default(CancellationToken))
        {
            Dictionary<string, int> failedAttempts = blobs.ToDictionary(k => k.Uri.ToString(), v => 0);
            bool pendingCopy = true;

            while (pendingCopy)
            {
                cancellationToken.ThrowIfCancellationRequested();

                pendingCopy = false;

                foreach (var dest in blobs)
                {
                    pendingCopy |= await IsCopyInProgress(dest, failedAttempts, cancellationToken);
                }

                if (pendingCopy)
                {
                    await Task.Delay(configuration.ReplicationStatusPollingInterval, cancellationToken);
                }
            }
        }

        private async Task<bool> IsCopyInProgress(ICloudBlob dest, IDictionary<string, int> failedAttempts, CancellationToken cancellationToken = default(CancellationToken))
        {
            bool pendingCopy = false;
            var destBlob = await dest.Container.GetBlobReferenceFromServerAsync(dest.Name, cancellationToken);

            switch (destBlob.CopyState.Status)
            {
                case CopyStatus.Aborted:
                case CopyStatus.Failed:

                    int numberOfFailes;
                    if (failedAttempts.TryGetValue(destBlob.Uri.ToString(), out numberOfFailes) &&
                        numberOfFailes < configuration.MaximumReplicationRetries)
                    {
                        pendingCopy = true;

                        await destBlob.StartCopyFromBlobAsync(destBlob.CopyState.Source, cancellationToken);
                        failedAttempts[destBlob.Uri.ToString()] = numberOfFailes + 1;
                    }
                    else
                    {
                        throw new Exception("Failed to replicate blob " + destBlob.Name);
                    }
                    break;
                case CopyStatus.Pending:
                    pendingCopy = true;
                    break;
                case CopyStatus.Success:
                    pendingCopy = false;
                    break;
                default:
                    throw new Exception("Undefined copy state");
            }

            return pendingCopy;
        }      
    }
In the above sample code we can see how to replicate the content to multiple location and how to ensure that copy action had finished with success. There is only one case that is not take into account: What happens if the process ends before replication action ends. How we can check that the replication was done with success?
This topic will be discussed tomorrow.
Enjoy!

Comments

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see

Navigating Cloud Strategy after Azure Central US Region Outage

 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provided a too