In addition to Weibo, there is also WeChat
Please pay attention
WeChat public account
Shulou
2025-01-25 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Servers >
Share
Shulou(Shulou.com)06/02 Report--
In the previous article, we learned about the type and size of Azure virtual machines, and then let's take a look at Azure disk storage and what disk storage is available in Azure.
Azure disk storage can be divided into managed and unmanaged disks in administrative mode.
Managed disk
Managed disks are a feature that simplifies disk management for Azure IaaS VM by handling storage account management, and Azure can create and manage disks simply by specifying the required disk type (standard HDD, standard SSD, or advanced SSD) and size. Azure managed disks are virtual hard disks (VHD). It can be thought of as a physical disk in the local server, but it is virtualized. Azure managed disks are stored as page blob, which is a random IO storage object in Azure. We call a managed disk "managed" because it is an abstraction of the page blob, blob container, and Azure storage account. For managed disks, all you have to do is preconfigure the disks, and Azure takes care of the rest. It allows us to maintain virtual machine disks without having to configure a "storage account", and the extended set (Scale Sets) allows hundreds of the same virtual machines to be deployed at once. Managed disks have many advantages, as follows
Simple and scalable VM deployment
Managed disks process storage behind the scenes. Previously, you had to create a storage account to store Azure VM's disks (VHD files). "when extending, you must ensure that additional storage accounts are created so that no disk exceeds the IOPS limit for storage." When using managed disks to process storage, it is no longer subject to storage account restrictions (for example, 20000 IOPS per account). In addition, you no longer need to copy custom images (VHD files) to multiple storage accounts. You can manage custom images (one storage account per Azure area) in a central location and use them to create hundreds of VM in a subscription.
Managed disks support the creation of up to 50000 VM disks of the same type in one subscription per region, which makes it possible to create tens of thousands of VM in a single subscription. This feature further increases the scalability of the virtual machine size set by allowing up to a thousand VM to be created in a single virtual machine size set using a market image.
Higher reliability of availability sets
Managed disks provide better reliability for availability sets by ensuring that the disks of the VM in the availability set are completely isolated from each other to avoid a single point of failure. The disk is automatically placed in a different storage scaling unit (module). If a module fails due to a hardware or software failure, only VM instances with its disks on that module will fail. For example, suppose an application is running on five VM and the VM is in one availability set. These VM disks are not stored in the same module, so if one module fails, other instances of the application can continue to run.
Highly durable and available
Azure disks have 99.999% availability. There are three copies of the data, and high persistence gives users peace of mind. If there is a problem with one or two of the copies, the remaining copies can ensure the persistence of the data and high tolerance to failures. This architecture helps Azure to continuously provide enterprise-class persistence for IaaS disks, with an annualized failure rate of 0%, reaching an industry-leading level.
Granular access control
You can use Azure role-based access control (RBAC) to assign specific permissions to managed disks to one or more users. Managed disks expose a variety of operations, including read, write (create / update), delete, and retrieve the disk's shared access signature (SAS) URI. You can grant access to only the actions that a person needs to perform his or her work. For example, if you do not want someone to copy a managed disk to a storage account, you can choose not to grant access to the export operation on that managed disk. Similarly, if you do not want someone to copy a managed disk using SAS URI, you can choose not to grant that permission to that managed disk.
Azure backup service support
Use the Azure backup service with managed disks to create backup jobs with time-based backups, easy VM restore, and backup retention policies. Managed storage only supports local redundant storage (LRS) as a replication option. Three copies of the data remain in the same area. For regional disaster recovery, you must use the Azure backup service and the GRS storage account as the backup vault to back up VM disks in different regions. Current Azure backups support disk sizes up to 4TB. To support 4TB disks, upgrade the VM backup stack to V2.
Microsoft recommends that all new virtual machines use managed disks and that all existing virtual machines be migrated to this mode.
Unmanaged disk
Unmanaged disks are traditional types of disks that VM has always used. Once you have these disks, you can create your own storage account and specify it when you create the disk. Make sure that you do not place too many disks in the same storage account, as it may exceed the scalability target of the storage account (for example, 20000 IOPS), resulting in a limit on the number of VM. When using unmanaged disks, you must determine how to maximize the use of one or more storage accounts to take full advantage of the performance of VM.
When creating a new virtual machine, the default is managed disk. To use unmanaged disk, you need to modify the settings, as shown in the following figure
Click No, and then you need to create a new or select a storage account
Divided by performance layer
Azure disks are currently available in four disk types: Super solid state drives (SSD, preview), advanced SSD, standard SSD, and standard hard disk drives (HDD). Three of them have been officially released (GA), and one is a preview version. Each of these four disk types has its own target customer scheme. The following table shows a comparison of these disk types:
Super SSD (preview version)
Advanced SSD
Standard SSD
Standard HDD
Disk Typ
SSD
SSD
SSD
HDD
Scene
IO-intensive workloads such as SAP HANA, top-level databases (for example, SQL, Oracle), and other transaction-intensive workloads.
Production and performance-sensitive workloads
Web servers, infrequently used enterprise applications, and development / testing
Backup, non-critical, infrequent access
Disk Siz
65536 GB (GiB) (preview version)
4095 GiB (GA), 32767 GiB (preview version)
4095 (GA) GiB, 32767 GiB (preview version)
4095 GiB (GA), 32767 GiB (preview version)
Maximum throughput
2000 MiB/ seconds (preview version)
250 (GA) MiB/ seconds, 750 MiB/ seconds (preview version)
60 MiB/ seconds (GA), 500 MiB/ seconds (preview version)
60 MiB/ seconds (GA), 500 MiB/ seconds (preview version)
Maximum IOPS
160000 (preview version)
7500 (GA), 20000 (preview version)
500 (GA), 2000 (preview version)
500 (GA), 2000 (preview version)
Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.
Views: 282
*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.
Continue with the installation of the previous hadoop.First, install zookooper1. Decompress zookoope
"Every 5-10 years, there's a rare product, a really special, very unusual product that's the most un
© 2024 shulou.com SLNews company. All rights reserved.