Skip to content

Commit afd1bbc

Browse files
authored
Merge pull request #263091 from roygara/simplifyUltra
Simplify ultra
2 parents 9e0e402 + 30d2abe commit afd1bbc

File tree

1 file changed

+16
-6
lines changed

1 file changed

+16
-6
lines changed

includes/managed-disks-ultra-disks-GA-scope-and-limitations.md

Lines changed: 16 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -4,16 +4,26 @@ description: include file
44
author: roygara
55
ms.service: azure-disk-storage
66
ms.topic: include
7-
ms.date: 12/05/2023
7+
ms.date: 01/22/2024
88
ms.author: rogarana
99
ms.custom: include file
1010
---
1111

12-
Ultra disks can't be used as OS disks, they can only be created as empty data disks. Ultra disks also can't be used with some features and functionality, including disk export, changing disk type, VM images, availability sets, or Azure disk encryption. The size of an Ultra Disk can't be expanded without either deallocating the VM or detaching the disk.Azure Site Recovery doesn't support ultra disks. In addition, only un-cached reads and un-cached writes are supported. Snapshots for ultra disks are available but have additional limitations. See [Incremental snapshots of Premium SSD v2 and Ultra Disks](../articles/virtual-machines/disks-incremental-snapshots.md#incremental-snapshots-of-premium-ssd-v2-and-ultra-disks) for details. Azure Backup support for VMs with Ultra Disks is currently in [public preview](../articles/backup/backup-support-matrix-iaas.md#vm-storage-support).
13-
14-
Ultra disks support a 4k physical sector size by default. A 512E sector size is available as a generally available offering with no sign-up required. While most applications are compatible with 4k sector sizes, some require 512 byte sector sizes. Oracle Database, for example, requires release 12.2 or later in order to support 4k native disks. For older versions of Oracle DB, 512 byte sector size is required.
15-
16-
The only infrastructure redundancy options currently available to ultra disks are availability zones. VMs using any other redundancy options cannot attach an ultra disk.
12+
The following list contains Ultra disks's limitations:
13+
- Can't be used as OS disks.
14+
- Doesn't support disk export.
15+
- Doesn't support VM images.
16+
- Doesn't support availability sets.
17+
- Doesn't support Azure disk encryption.
18+
- Doesn't support Azure Site Recovery.
19+
- Doesn't support disk caching.
20+
- Must deallocate your VM or detach your ultra disk in order to expand your Ultra Disk
21+
- Existing disks currently can't change their type to an Ultra Disk. They must be [migrated](../articles/virtual-machines/disks-convert-types.md#migrate-to-premium-ssd-v2-or-ultra-disk).
22+
- Currently only supports Single VM and Availability zone infrastructure options.
23+
- Snapshots are supported with [additional limitations](../articles/virtual-machines/disks-incremental-snapshots.md#incremental-snapshots-of-premium-ssd-v2-and-ultra-disks).
24+
- Azure Backup supports VMs with Ultra Disks as a [public preview](../articles/backup/backup-support-matrix-iaas.md#vm-storage-support).
25+
26+
Ultra disks support a 4k physical sector size by default but also supports a 512E sector size. Most applications are compatible with 4k sector sizes, but some require 512 byte sector sizes. Oracle Database, for example, requires release 12.2 or later in order to support 4k native disks. For older versions of Oracle DB, 512 byte sector size is required.
1727

1828
The following table outlines the regions ultra disks are available in, as well as their corresponding availability options.
1929

0 commit comments

Comments
 (0)