Premium SSD v2 disks are recommended for the use as data disks with FlashGrid Cluster in those regions where they are available. This article provides necessary steps to create new disks and additional details regarding their usage.
Prerequisites
To use Premium SSD v2 in the regions that do not have Availability Zones, please run the following Azure CLI command to enable Premium SSD v2 with Availability Sets at your subscription level:
az feature registration create --namespace Microsoft.Compute --name PV2WithAVSetRegionWithoutZone
Creating and attaching Premium SSD v2
Create and attach disks using the Azure CLI (Azure CLI version should be 2.38.0 or later, use az --version to check). It is not recommended to use Azure Portal GUI for creating v2 disks.
-
Create a new disk (the sector size must be set to 512 as in the command below):
az disk create --sku PremiumV2_LRS \ --encryption-type EncryptionAtRestWithPlatformKey \ --os-type Linux \ --logical-sector-size 512 \ --resource-group <resource_group> \ --name <disk_name, e.g. disks_rac1_lun10> \ --disk-iops-read-write <disk_iops, e.g. 16000> \ --disk-mbps-read-write <disk_mbps, e.g. 1200> \ --size-gb <size_gb, e.g. 1000> \ --location <location, e.g. eastus> \ --zone <zone, e.g. 1. Do not specify this option if the region does not support availability zones>See Premium SSD v2 performance for details on setting size, IOPS, MBPS.
-
Attach the disk:
az vm disk attach --caching None \ --resource-group <resource_group> \ --vm-name <vm_name, e.g. rac1> \ --disks <disk_name, e.g. disks_rac1_lun10> \ --lun <lun_number, e.g. 10>
Usage notes
- Premium SSD v1 and v2 should not be combined in the same disk group, except temporarily when doing migration from v1 to v2.
- IOPS and MBPS settings must be the same for all disks in the same diskgroup.
Limitations
- Premium SSD v2 disks may be unavailable in some regions.