Skip to content

Commit a17e002

Browse files
committed
Updates.
1 parent 22e6825 commit a17e002

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.author: rogarana
1010
ms.custom: include file
1111
---
1212

13-
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. Azure Backup and Azure Site Recovery do not support ultra disks. In addition, only un-cached reads and un-cached writes are supported. Currently, only incremental snapshots are available for ultra disks, as a preview. Full snapshots aren't currently supported.
13+
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. Azure Backup and Azure Site Recovery do not support ultra disks. In addition, only un-cached reads and un-cached writes are supported.
1414

1515
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.
1616

0 commit comments

Comments
 (0)