Azure Storage Blob Tutorial

This Azure tutorial explains, Azure storage blob, how to move data to Azure blob storage, how to create a blob storage account in Microsoft Azure?

Azure Storage Blob

Azure storage blob stores large amounts of unstructured object data, such as text or binary data. Blob Azure storage is highly scalable and available. Customers can access data objects in Blob storage with PowerShell or Azure CLI, programmatically through Azure storage client libraries.

The Blob storage offers three types of resources which are:

  • The storage account
  • A container in the storage account
  • A blob in a container

The Azure Storage service supports three types of blob:

  • The Block blob stores only text and binary data, up to about 4.7 TB. They are made up of data blocks that can be managed individually.
  • Add blobs consist of blocks, like block blobs, but are optimized for add operations. Addition blobs are great for scenarios such as logging data from virtual machines.
  • Page blob objects store random access files up to 8 TB in size. Page blob objects store virtual hard disk files and serve as disks for Azure virtual machines.

Move data to Blob storage

Several solutions exist to migrate existing data to Blob storage:

AzCopy is an easy-to-use command-line tool for Windows and Linux that copies data to and from Blob storage, between containers or between storage accounts. Azure Data Factory supports copying data to and from Blob storage with an account key, shared access signature, service principal, or managed identities for Azure resources.

Blobfuse is a virtual file system driver for Blob Azure Storage. You can use blobfuse to access your existing block blob data in your storage account via the Linux file system.

The Azure Data Box service makes it possible to transfer local data to Blob storage when large data sets or network constraints make it impossible to load data via the network.

Depending on the size of your data, you can request Azure Data Box Disk, Azure Data Box or Azure Data Box Heavy devices from Microsoft. You can then copy your data to these devices and send it to Microsoft, which will load it into Blob storage.

The Azure Import / Export service provides a way to import and export large amounts of data to and from your storage account using the hard drives you provide.

How to create a Blob Storage account

Create a storage account. Each storage account must belong to an Azure resource group. A resource group is a logical container used to group your Azure services. When you create a storage account, you have the choice between creating a resource group or using an existing resource group. This article demonstrates how to create a resource group.

To create a general purpose storage account v2 in the Azure portal, do the following:

Choose the subscription in which you want to create the storage account. In the Azure Portal, choose the Create resource button, then choose Storage account. Under the Resource Group field, select Create. Enter the name of your new resource group.

Azure Storage Blob

A resource group is a logical container used to group your Azure services. When you create a storage account, you have the choice between creating a resource group or using an existing resource group.

Then enter a name for your storage account. The name chosen must be unique throughout Azure. The name must also contain between 3 and 24 characters, and only lowercase letters and numbers.

Choose a location.
Make sure StorageV2 (general purpose v2) is selected in the Account type drop-down list.

Optionally modify the values of each of these fields: Performance, Replication, Access level. To learn more about these options, see Overview of Azure Storage.

Select the Advanced tab.

In the Data Lake Storage Gen2 section, set Hierarchical namespace to Enabled. Click Check + Create to create the storage account.

Your storage account is created now, through the portal.

Delete resources
To delete a resource group from the Azure portal:

On the Azure portal, expand the left menu to open the services menu, and select Resource groups to display the list of your resource groups.

create a Blob Storage account

Find the resource group to delete, then right-click the More button (…) to the right of the list, Select Delete resource group and confirm.

The storage system is a very flexible backup software that includes a full set of features for backup to Cloud spaces. It allows online backups to Azure Storage, which is part of the Microsoft cloud platform. Azure backup can be done in a fully automated way, and includes powerful built-in features, such as database backup, open file backup (VSS), compression and
encryption, email notifications, etc.

In addition to Microsoft Azure, The storage system also supports all the main cloud storage services: Amazon S3, Onedrive, Google Drive and Dropbox.

When adding a destination to cloud storage like Azure, you must first create a specific account in The storage system. To do this, you must obtain the special identification information provided in the Microsoft Azure management console (Microsoft Azure requires a subscription that allows you to try all Azure features for a trial period).

After creating an Azure account (or if you already have one), access your management console at the following address:

Here you can activate the “Storage” function, create “containers” where to place your files, download your files (up and down) using an ergonomic web interface. In order for the storage system to be able to send files to this space, you must copy the authentication codes and paste them when setting
up the account in the storage system.

Once you have retrieved the account name and associated access key, add a cloud destination in the storage system, and create a new Microsoft Azure account. You need to select an account from a drop-down list. To add or modify an account, simply click on the dedicated button near the list.

In this window, you can easily configure all the destination parameters, such as the name of the container, the number of copies to keep, AES encryption and/or a zip password, bandwidth limitation, etc.

In the following tabs, you can configure a scheduler to run the backup automatically on the days and times of your choice, and email notifications, to be always informed of the outcome of your backups and possible errors.

With Azure Backup, you can automate online backup of your important documents and files in a very simple way. In addition, you can back up databases such as SQL Server or MySQL to a secure cloud, remotely, with the highest security available today, thanks to the secure HTTPS protocol, AES encryption and the fact that your backup is found source data in a
different geographic areas, safe from thieves, equipment failures and natural disasters.

Azure File Sync

Azure File Sync promotes the effectiveness of centralization on your organization’s file shares without losing the flexibility, performance, and compatibility of a local file server. To do this, Azure File Sync turns your Windows servers into a quick cache of your Azure file share.

Multiple server endpoints can be on the same volume if their namespaces do not overlap (for example, F: \ sync1 and F: \ sync2). You can configure cloud prioritization policies individually for each server endpoint. If you add a server location with an existing set of files as the server endpoint to a synchronization group, those files are merged with any other files already
present on the other endpoints in the synchronization group.

How to deploy Azure File Sync


To create a server endpoint, you must first verify that the following criteria are met:

The Azure file synchronization agent is installed on the server and the server has been registered. You can find instructions for installing the Azure File Sync agent in the article, Registering/unregistering a server with Azure File Sync.

Verify that a storage synchronization service has been deployed. See the How to Guide to Deploy Azure File Sync.

Verify that a synchronization group has been deployed. Find out how [Create a synchronization group] ( # create-a sync-group-and a-cloud-endpoint).

Check that the server is connected to the Internet and that Azure is accessible. use port 443 for all communications between the server and our service.

Add a server endpoint

To add a server endpoint, go to the desired synchronization group, then select “Add Server Endpoint”.

Add a new server endpoint in the Synchronization Group pane

The following information is required under the Add Server Endpoint option:

Registered server: name of the server or cluster on which to create the server endpoint.

  • Path: Path on the Windows Server to be synchronized as part of the synchronization group.
  • Cloud prioritization: switch to enable or disable cloud prioritization. When enabled, cloud tiering prioritizes files in your Azure file shares. Local file shares are then converted to a cache, rather than a full copy of the dataset, to help you optimize space on your server.
  • Volume Free Space: The amount of free space to reserve on the volume where the server endpoint is located. For example, if the volume’s free space is set to 50% on a volume with a single server endpoint, about half of the amount of data will be prioritized in Azure Files. Whether cloud prioritization is enabled or not, Azure file
    sharing always has a full copy of the data in the sync group.

Select Create to add the server endpoint. Files located in a synchronization group namespace will now be synchronized.

Remove a server endpoint

If you no longer want to use Azure File Sync for a given server endpoint, you can delete the server endpoint.

[! Warning]
Do not attempt to resolve synchronization, cloud prioritization, or any other aspect of Azure File Sync by removing and recreating the server endpoint unless specifically requested by a Microsoft engineer. Deleting a server endpoint is destructive, and tiered files on the server endpoint are not “reconnected” to their location on the Azure file share after the server endpoint is recreated, which results in synchronization errors. Also, note that tiered files that exist outside of the server endpoint namespace may be permanently lost.

Hierarchical files can exist in your server endpoint even if cloud prioritization has never been enabled.

To ensure that all tiered files are recalled before removing the server endpoint, turn off cloud tiering on the server endpoint, and then run the following PowerShell cmdlet to recall all tiered files within the server. The namespace for your server endpoint:

Import-Module "C: \ Program Files \ Azure \ StorageSyncAgent \
Invoke-StorageSyncFileRecall -Path <path-to-to-your-server-endpoint> -Order CloudTieringPolicy

Specify -Order CloudTieringPolicy first recalls recently modified files. Other optional but useful parameters to consider are:

-ThreadCount determines the number of files recalled in parallel.
-PerFileRetryCount determines how often a callback to a currently blocked file is attempted.
-PerFileRetryDelaySeconds determines the time, in seconds, between recall attempts, and should always be used with the previous parameter.

To remove the server endpoint

Access the storage synchronization service to which your server is registered. Go to the desired synchronization group.

Remove the desired server endpoint from the synchronization group in the Storage Synchronization service. To do this, you can right-click the affected server endpoint in the Synchronization Group pane.

You may like following Microsoft Azure tutorials:

This tutorial, we learned azure storage blob and how to create azure storage blob, how to move data to blob storage. How to do Azure file sync and how to deploy azure file sync.