Azure Storage Components | Intellipaat
Some of the storage services are described further below.
Azure Storage Components
The Azure storage account is the foundation of the Azure storage service. The Storage account serves as an administrative container for the majority of Azure storage services. All of the storage services are described further below.
Azure Blob: Within the storage account, we can have Azure Blob storage, which is used to store unstructured data such as media files, documents, and so on.
Azure file: If we want to share files between two virtual machines, we can create an Azure file share and access it from both of the virtual machines. We can share data between two or more virtual machines.
Archive: Archive was just introduced and is currently in preview. We can use the archive to reduce costs. As a result, we can move any infrequently accessed blobs or files into the archive to reduce costs. However, once the data is moved to an archive, it will take some time to recover that data.
Azure Queues: It is capable of storing messages.
Azure Table: It can be used to store entities in Azure Table. The Azure Table is not the same as the SQL table. The schema within the table is not enforced in this NoSQL datastore.
Azure Disk Storage: Any operating system disc associated with the virtual machine in Azure is saved in a disc storage account. Furthermore, any OS image from which this OS disc is generated is saved as a.vhd file on the disc storage.
Azure Storsimple: Azure provides Storsimple as a hybrid cloud storage solution. Storsimple is a SAN (Storage Area Network)-based hybrid storage solution. It used to be a separate company, but Microsoft absorbed it and now provides the same services as part of Azure and from a disaster recovery (DR) standpoint.
Azure Site Recovery: If we want to use Azure as a disaster recovery (DR) data centre, we can use Azure site recovery to replicate workloads from our on-premises data centre into Azure. Workloads that have been replicated will be saved as images in a storage account. When our on-premises data centre is unavailable, we can run some automated scripts that take into account the most recent image and create a virtual machine.
Azure Data Box: If we have terabytes of data to transfer from an on-premises data centre to Azure and we don't want to use a network because transferring data over a network in terabytes is not feasible. In that case, we can make use of the Azure data box. We can load the data into the data box and give it to Microsoft by using Azure Data Box. Microsoft will upload that information to Azure.
Azure Backup: We can use Azure Backup to backup our virtual machine's discs into a recovery service vault and then restore the machine using that image. We must keep in mind that Azure backup does not use storage to store the disc image. They are kept in the vault for recovery services.
Azure Monitor: Azure Monitor can be used to monitor all of these services. We can use Azure Monitor for basic monitoring and log analytics for more advanced monitoring and analysis. We can also use alerts if we want to be notified when certain things happen. For example, if the file share capacity reaches its limit, we can configure it so that we are notified.
CDN (Content Delivery Network): This network is used to deliver the contents of the storage account. To reduce delivery latency, we can use a content delivery network. To reduce latency, we'll set up a CDN endpoint near the users.
. . . . . . . . . . . .




Comments
There are no comments for this story
Be the first to respond and start the conversation.