Skip to content

Commit d7715ed

Browse files
committed
Update some details
1 parent 3c0e083 commit d7715ed

File tree

1 file changed

+4
-7
lines changed

1 file changed

+4
-7
lines changed

articles/sap/workloads/dbms-guide-oracle.md

Lines changed: 4 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -168,12 +168,9 @@ Oracle ASM disk group recommendation:
168168

169169
### Variant 2 – medium to large data volumes between 3 TB and 12 TB, restore time important
170170

171-
Customer has medium to large sized databases where backup and/or restore
172-
+
171+
Customer has medium to large sized databases where backup and/or restore, or recovery of all databases can't be accomplished in a timely fashion.
173172

174-
recovery of all databases can't be accomplished in a timely fashion.
175-
176-
Usually customers are using RMAN, Azure Backup for Oracle and/or disk snap techniques in combination.
173+
Usually customers are using RMAN, Azure Backup for Oracle and/or disk snapshot techniques in combination.
177174

178175
Major differences to Variant 1 are:
179176

@@ -198,7 +195,7 @@ Major differences to Variant 1 are:
198195

199196
### Variant 3 – huge data and data change volumes more than 5 TB, restore time crucial
200197

201-
Customer has a huge database where backup and/or restore + recovery of a single database can't be accomplished in a timely fashion.
198+
Customer has a huge database where backup and/or restore, or recovery of a single database can't be accomplished in a timely fashion.
202199

203200
Usually customers are using RMAN, Azure Backup for Oracle and/or disk snap techniques in combination. In this variant, each relevant database file type is separated to different Oracle ASM disk groups.
204201

@@ -346,7 +343,7 @@ The disk selection for hosting Oracle's online redo logs is driven by IOPS requi
346343
### Current recommendations for Oracle Storage
347344

348345
1. Azure Premium Storage – Most customers are deploying on ASM with Premium Storage
349-
2. Azure NetApp Files - VLDB customers, often with single Oracle databases larger than 50TB are typically using ANF and leveraging Storage Snapshot capabilities of Azure NetApp Files for Backup and Restore
346+
2. Azure NetApp Files - VLDB customers, often with single Oracle databases larger than 50TB are typically using ANF and using Storage Snapshot capabilities of Azure NetApp Files for Backup and Restore
350347
3. Managed Disk Bursting - [Managed disk bursting - Azure Virtual Machines \| Microsoft Docs](/azure/virtual-machines/disk-bursting)
351348
4. Azure Write Accelerator - used for the case that the Oracle redo log is based on Premium SSD v1 disks
352349
5. Online disk extension is fully supported for Premium Storage v1 and works with ASM

0 commit comments

Comments
 (0)