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: articles/storage/common/storage-introduction.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -56,13 +56,13 @@ The following table compares Azure Storage services and shows example scenarios
56
56
| Feature | Description | When to use |
57
57
|--------------|-------------|-------------|
58
58
|**Azure Files**|Offers fully managed cloud file shares that you can access from anywhere via the industry standard [Server Message Block (SMB) protocol](/windows/win32/fileio/microsoft-smb-protocol-and-cifs-protocol-overview), [Network File System (NFS) protocol](https://en.wikipedia.org/wiki/Network_File_System), and [Azure Files REST API](/rest/api/storageservices/file-service-rest-api).<br><br>You can mount Azure file shares from cloud or on-premises deployments of Windows, Linux, and macOS. | You want to "lift and shift" an application to the cloud that already uses the native file system APIs to share data between it and other applications running in Azure.<br/><br/>You want to replace or supplement on-premises file servers or NAS devices.<br><br> You want to store development and debugging tools that need to be accessed from many virtual machines. |
59
+
|**Azure NetApp Files**| Offers a fully managed, highly available, enterprise-grade NAS service that can handle the most demanding, high-performance, low-latency workloads requiring advanced data management capabilities. | You have a difficult-to-migrate workload such as POSIX-compliant Linux and Windows applications, SAP HANA, databases, high-performance compute (HPC) infrastructure and apps, and enterprise web applications. <br></br> You require support for multiple file-storage protocols in a single service, including NFSv3, NFSv4.1, and SMB3.1.x, enables a wide range of application lift-and-shift scenarios, with no need for code changes. |
59
60
|**Azure Blobs**| Allows unstructured data to be stored and accessed at a massive scale in block blobs.<br/><br/>Also supports [Azure Data Lake Storage Gen2](../blobs/data-lake-storage-introduction.md) for enterprise big data analytics solutions. | You want your application to support streaming and random access scenarios.<br/><br/>You want to be able to access application data from anywhere.<br/><br/>You want to build an enterprise data lake on Azure and perform big data analytics. |
60
61
|**Azure Elastic SAN**| Azure Elastic SAN is a fully integrated solution that simplifies deploying, scaling, managing, and configuring a SAN, while also offering built-in cloud capabilities like high availability. | You want large scale storage that is interoperable with multiple types of compute resources (such as SQL, MariaDB, Azure virtual machines, and Azure Kubernetes Services) accessed via the [internet Small Computer Systems Interface](https://en.wikipedia.org/wiki/ISCSI) (iSCSI) protocol.|
61
62
|**Azure Disks**| Allows data to be persistently stored and accessed from an attached virtual hard disk. | You want to "lift and shift" applications that use native file system APIs to read and write data to persistent disks.<br/><br/>You want to store data that isn't required to be accessed from outside the virtual machine to which the disk is attached. |
62
63
|**Azure Container Storage** (preview) | Azure Container Storage (preview) is a volume management, deployment, and orchestration service that integrates with Kubernetes and is built natively for containers. | You want to dynamically and automatically provision persistent volumes to store data for stateful applications running on Kubernetes clusters. |
63
64
|**Azure Queues**| Allows for asynchronous message queueing between application components. | You want to decouple application components and use asynchronous messaging to communicate between them.<br><br>For guidance around when to use Queue Storage versus Service Bus queues, see [Storage queues and Service Bus queues - compared and contrasted](../../service-bus-messaging/service-bus-azure-and-service-bus-queues-compared-contrasted.md). |
64
65
|**Azure Tables**| Allows you to store structured NoSQL data in the cloud, providing a key/attribute store with a schemaless design. | You want to store flexible datasets like user data for web applications, address books, device information, or other types of metadata your service requires. <br/><br/>For guidance around when to use Table Storage versus Azure Cosmos DB for Table, see [Developing with Azure Cosmos DB for Table and Azure Table Storage](../../cosmos-db/table-support.md). |
65
-
|**Azure NetApp Files**| Offers a fully managed, highly available, enterprise-grade NAS service that can handle the most demanding, high-performance, low-latency workloads requiring advanced data management capabilities. | You have a difficult-to-migrate workload such as POSIX-compliant Linux and Windows applications, SAP HANA, databases, high-performance compute (HPC) infrastructure and apps, and enterprise web applications. <br></br> You require support for multiple file-storage protocols in a single service, including NFSv3, NFSv4.1, and SMB3.1.x, enables a wide range of application lift-and-shift scenarios, with no need for code changes. |
Copy file name to clipboardExpand all lines: articles/virtual-machines/workloads/oracle/oracle-database-backup-strategies.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,6 +47,8 @@ The Azure Storage platform includes the following data services that are suitabl
47
47
48
48
-**Azure Blob Storage**: An object store for text and binary data. It also includes support for big data analytics through Azure Data Lake Storage Gen2.
49
49
50
+
-**Azure NetApp Files**: Complete networked storage solution including advanced data management capabilities for taking snapshots, cloning, and replicating database volumes.
51
+
50
52
-**Azure Files**: Managed file shares for cloud or on-premises deployments.
51
53
52
54
-**Azure Disk Storage**: Block-level storage volumes for Azure VMs.
Copy file name to clipboardExpand all lines: articles/virtual-machines/workloads/oracle/oracle-overview.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -84,10 +84,13 @@ With Oracle Active Data Guard, you can achieve high availability with a primary
84
84
85
85
To walk through the basic setup procedure on Azure, see [Implement Oracle Golden Gate on an Azure Linux VM](configure-oracle-golden-gate.md).
86
86
87
+
You can effectively achieve high availability for your Oracle databases by using the storage-based replication functionality of Azure NetApp Files, which is one of the added data management values of this service. Azure NetApp Files volumes can be replicated to another region using [cross-region replication](../../../azure-netapp-files/cross-region-replication-introduction.md) or to another zone within the region using [cross-zone replication](../../../azure-netapp-files/cross-zone-replication-introduction.md).
88
+
87
89
In addition to having a high availability and disaster recovery solution architected in Azure, you should have a backup strategy in place to restore your database.
88
90
## Backup Oracle workloads
89
91
Different [backup strategies](oracle-database-backup-strategies.md) are available for Oracle on Azure VMs, the following backups are other options:
90
92
- Using [Azure files](oracle-database-backup-azure-storage.md)
93
+
- Using [Azure NetApp Files](oracle-database-backup-strategies.md#azure-netapp-files)
91
94
- Using [Azure backup](oracle-database-backup-azure-backup.md)
92
95
- Using [Oracle RMAN Streaming data](oracle-rman-streaming-backup.md) backup
Copy file name to clipboardExpand all lines: articles/virtual-machines/workloads/oracle/oracle-reference-architecture.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -233,6 +233,7 @@ Patching your virtual machine operating system can be automated using [Azure Aut
233
233
- Consider using ultra disks when available or premium disks for your Oracle database.
234
234
- Consider setting up a standby Oracle database in another Azure region using Oracle Data Guard.
235
235
- Consider using [proximity placement groups](../../co-location.md#proximity-placement-groups) to reduce the latency between your application and database tier.
236
+
- Azure VMs throttle network bandwidth at higher throughput levels than managed disk. You can achieve higher throughput on the same VM SKU or use a smaller VM SKU for the same throughput using networked storage for the database such as [Azure NetApp Files](../../../azure-netapp-files/azure-netapp-files-introduction.md).
236
237
- Set up [Oracle Enterprise Manager](https://docs.oracle.com/en/enterprise-manager/) for management, monitoring, and logging.
237
238
- Consider using Oracle Automatic Storage Management for streamlined storage management for your database.
238
239
- Use [Azure Pipelines](/azure/devops/pipelines/get-started/what-is-azure-pipelines) to manage patching and updates to your database without any downtime.
0 commit comments