You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: learn-pr/wwl-azure/design-data-storage-solution-for-non-relational-data/includes/4-design-for-data-redundancy.md
+6-1Lines changed: 6 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -55,9 +55,14 @@ You review the different options for implementing replication. Data redundancy i
55
55
56
56
-**Consider zone-redundant storage**. Choose ZRS for excellent performance, low latency, and resiliency for your data if it becomes temporarily unavailable. Keep in mind that ZRS by itself might not protect your data against a regional disaster where multiple zones are permanently affected.
57
57
58
+
58
59
-**Consider secondary regions**. For applications requiring high durability, you can choose to additionally copy the data in your storage account to a secondary region that is hundreds of miles away from the primary region. If your storage account is copied to a secondary region, then your data is durable even if a complete regional outage or a disaster in which the primary region isn't recoverable.
59
60
60
61
-**Consider read access requirements**. Identify Tailwind Traders applications that require read access to the replicated data in the secondary region, if the primary region becomes unavailable for any reason. Configure your storage account with read access to the secondary region. Your applications can seamlessly shift to reading data from the secondary region if the primary region becomes unavailable.
61
62
63
+
64
+
> [!Note]
65
+
> The Archive access tier for Blob Storage isn't supported for ZRS, GZRS, or RA-GZRS accounts. If your storage account contains archived blobs, you must rehydrate them to an online tier before converting to zone-redundant storage.
66
+
62
67
> [!TIP]
63
-
> Continue your learning with the [Describe Azure storage services](/training/modules/describe-azure-storage-services/) training module.
68
+
> Continue your learning with the [Describe Azure storage services](/training/modules/describe-azure-storage-services/) training module.
Copy file name to clipboardExpand all lines: learn-pr/wwl-azure/design-data-storage-solution-for-non-relational-data/includes/6-design-for-azure-files.md
+14-2Lines changed: 14 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,7 @@ Azure file shares can be used in two ways. You can directly mount serverless Azu
28
28
29
29
Because Azure Files stores files in a storage account, you can [choose your performance level](/azure/storage/files/storage-files-scale-targets). Performance metrics differ between standard and premium storage account levels. Premium accounts offer lower latency and higher IOPS and bandwidth.
30
30
31
-
Standard performance accounts use HDD to store data. With HDD, the costs are lower but so is the performance. SSD arrays back the premium storage account's performance, which comes with higher costs. Currently, premium accounts can only use file storage accounts with ZRS storage in a limited number of regions.
31
+
Standard performance accounts use HDD to store data. With HDD, the costs are lower but so is the performance. SSD arrays back the premium storage account's performance, which comes with higher costs. SSD file shares support LRS and ZRS redundancy. Geo-redundant options (GRS and GZRS) are only available for HDD file shares.
32
32
33
33
#### Determine your storage tier
34
34
@@ -42,6 +42,16 @@ Azure Files offers four tiers of storage. These tiers allow you to tailor your f
42
42
43
43
-**Cool access tier**: Cost-efficient storage optimized for online archive storage scenarios. Offered on storage hardware using HDDs.
44
44
45
+
#### Choose your billing model
46
+
47
+
Azure Files supports three billing models that affect how storage costs are calculated.
48
+
49
+
-**Provisioned v2 (recommended)**. Allows you to independently set the storage capacity, IOPS, and throughput for your file share. Available for both SSD and HDD file shares. Provisioned v2 is recommended for new deployments.
50
+
51
+
-**Pay-as-you-go**. Charges are based on actual usage for transactions and storage. Available for HDD file shares only. Useful for workloads with unpredictable access patterns.
52
+
53
+
-**Provisioned v1 (legacy)**. Storage, IOPS, and throughput scale together in a fixed ratio. Available for SSD file shares only.
54
+
45
55
### Things to consider when choosing your implementation
46
56
47
57
[Your decision about which technology](/azure/storage/common/nfs-comparison) to implement depends on your business use cases, the protocols required for your files, and your performance goals. We review considerations for using Azure Blob Storage and Azure Files. Another option is to use [Azure NetApp Files](/azure/azure-netapp-files/), which is a fully managed, highly available, enterprise-grade NAS service. Azure NetApp Files can handle the most demanding, high-performance, low-latency workloads. You can migrate workloads that are deemed "unmigratable."
@@ -55,5 +65,7 @@ The following table compares features and uses cases for these three implementat
|**Performance (per volume)**| Up to 20,000 IOPS. Up to 15 GiB/s throughput. | Up to 100,000 IOPS. Up to 10 GiB/s throughput | Up to 460,000 IOPS. Up to 4.5 GiB/s throughput for regular volumes. Up to 10 GiB/s throughput for large volumes. |
57
67
68
+
69
+
58
70
> [!TIP]
59
-
> Learn more about file based workloads in the [Introduction to Azure NetApp Files](/training/modules/introduction-to-azure-netapp-files/) training module.
71
+
> Learn more about file based workloads in the [Introduction to Azure NetApp Files](/training/modules/introduction-to-azure-netapp-files/) training module.
Copy file name to clipboardExpand all lines: learn-pr/wwl-azure/design-data-storage-solution-for-non-relational-data/includes/7-design-for-azure-disk-solutions.md
+11-9Lines changed: 11 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,18 +1,18 @@
1
1
Azure offers many disk solutions. In this module, we examine how to work with data disks by using Azure managed disks.
2
2
3
-
Data disks are used by virtual machines to store data like database files, website static content, or custom application code. The number of data disks you can add depends on the virtual machine size. Each data disk has a maximum capacity of 32,767 GB.
3
+
Data disks are used by virtual machines to store data like database files, website static content, or custom application code. The number of data disks you can add depends on the virtual machine size.
4
4
5
5
> [!Tip]
6
6
> Microsoft recommends always using [Azure managed disks](/azure/virtual-machines/managed-disks-overview). You specify the disk size, the disk type, and provision the disk. Azure handles the remaining operations.
7
7
8
8
### Things to know about managed disks
9
9
10
-
Azure offers several types of managed disks. The following table shows a [comparison of four data disk types](/azure/virtual-machines/disks-types#disk-type-comparison).
10
+
Azure offers several types of managed disks. The following table shows a [comparison of data disk types](/azure/virtual-machines/disks-types#disk-type-comparison).
11
11
12
-
| Comparison | Ultra-disk | Premium SSD | Standard SSD | Standard HDD |
13
-
| --- | --- | --- | --- | --- |
14
-
|**Disk type**| SSD | SSD | SSD | HDD |
15
-
|**Scenario**| IO-intensive workloads, such as SAP HANA, top tier databases like SQL Server and Oracle, and other transaction-heavy workloads | Production and performance sensitive workloads | Web servers, Lightly used enterprise applications, development, and testing | Backup, Noncritical, Infrequent access |
12
+
| Comparison | Ultra-disk | Premium SSD v2 | Premium SSD | Standard SSD | Standard HDD |
13
+
| --- | --- | --- | --- | --- | ---|
14
+
|**Disk type**| SSD | SSD | SSD |SSD |HDD |
15
+
|**Scenario**| IO-intensive workloads, such as SAP HANA, top tier databases like SQL Server and Oracle, and other transaction-heavy workloads | Production and performance-sensitive workloads that consistently require low latency and high IOPS and throughput | Production and performance sensitive workloads | Web servers, Lightly used enterprise applications, development, and testing | Backup, Noncritical, Infrequent access |
16
16
17
17
#### Choose an encryption option
18
18
@@ -34,12 +34,14 @@ Think about what data disk types are needed for Tailwind Traders. Consider your
34
34
35
35
-**Premium SSD storage**: Azure Premium SSD-managed disks provide high throughput and IOPS with low latency. These disks offer a slightly less performance compared to Ultra Disk Storage. Premium SSD storage is available in all regions.
36
36
37
+
-**Premium SSD v2 storage**: Azure Premium SSD v2 managed disks offer higher performance than Premium SSDs and are less costly. You can independently tune capacity, IOPS, and throughput at any time without downtime. Premium SSD v2 is recommended for most general purpose workloads, including databases and gaming applications. Premium SSD v2 isn't available in all regions.
38
+
37
39
-**Standard SSD**: Azure Standard SSD-managed disks are a cost-effective storage option for VMs that need consistent performance at lower speeds. Standard SSD disks aren't as fast as Premium SSD disks or Ultra Disk Storage. You can attach Standard SSD disks to any VM.
38
40
39
-
-**Standard HDD**: In Azure Standard HDD-managed disks, data is stored on conventional magnetic disk drives that have moving spindles. Disks are slower and the variation in speeds is higher compared to solid-state drives (SSDs). Like Standard SSD disks, you can use Standard HDD disks for any VM.
41
+
-**Standard HDD**: In Azure Standard HDD-managed disks, data is stored on conventional magnetic disk drives that have moving spindles. Disks are slower and the variation in speeds is higher compared to solid-state drives (SSDs). You can use Standard HDD disks for data disks on any VM. Standard HDD support for OS disks is being retired on September 8, 2028.
40
42
41
43
-**Consider data caching**. Improve performance with disk caching. Azure Virtual Machines [disk caching](/azure/virtual-machines/premium-storage-performance#disk-caching) optimizes read and write access to the virtual hard disk (VHD) files. The VHDs are attached to Azure Virtual Machines. For OS disks, the default cache setting is `ReadWrite`, and for data disks, the default is `ReadOnly`.
42
44
43
-
> [!Warning]
44
-
> Disk caching isn't supported for disks 4 TiB and larger. When multiple disks are attached to your Virtual Machine, each disk smaller than 4 TiB supports caching. Changing the cache setting of an Azure disk, detaches and reattaches the target disk. When it's the OS disk, the VM is restarted.
45
+
> [!Warning]
46
+
> Disk caching isn't supported for disks 4 TiB and larger. When multiple disks are attached to your Virtual Machine, each disk smaller than 4 TiB supports caching. Changing the cache setting of an Azure disk, detaches and reattaches the target disk. When it's the OS disk, the VM is restarted.
0 commit comments