|
1 | | -- description: Implement cross-AZ replication strategy for Oracle to meet your workload requirements |
| 1 | +- description: Implement Oracle Data Guard replication across availability zones(AZs) to meet your workload's BCDR requirements |
2 | 2 | aprlGuid: ccf0fece-27c7-4163-98ce-a1dd982d7f79 |
3 | 3 | recommendationTypeId: null |
4 | 4 | recommendationControl: BusinessContinuity |
5 | 5 | recommendationImpact: High |
6 | 6 | recommendationResourceType: Microsoft.Subscription/subscriptions |
7 | 7 | recommendationMetadataState: Active |
8 | 8 | longDescription: |
9 | | - Define a BCDR strategy based on workload RPO/RTO. |
10 | 9 | Oracle Database@Azure follows a Silver-level reference architecture that provides high availability by default however it is vulnerable to AZ failures. |
11 | 10 | Gold-level adds Data Guard replication across AZs via Automated DG or manual setup. |
| 11 | + Data Guard transport mode - Use SYNC for zero data loss, or ASYNC when performance is constrained and a near-zero RPO is acceptable. |
12 | 12 | potentialBenefits: Ensure business continuity in case of zonal failure. |
13 | 13 | pgVerified: false |
14 | 14 | automationAvailable: no |
|
26 | 26 | recommendationMetadataState: Active |
27 | 27 | longDescription: |
28 | 28 | Gold-level reference architecture with Oracle Database@Azure is recommended, meaning that database changes will be replicated via Data Guard (ASYNC replication) to a secondary Oracle Database@Azure instance in a different region. |
29 | | - potentialBenefits: The cloud MAA architecture achieves data protection and DR. |
| 29 | + potentialBenefits: The cloud Maximum Availability Architecture achieves data protection and DR. |
30 | 30 | pgVerified: false |
31 | 31 | automationAvailable: no |
32 | 32 | tags: [ORACLE] |
|
35 | 35 | url: "https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/scenarios/oracle-iaas/oracle-disaster-recovery-oracle-database-azure" |
36 | 36 |
|
37 | 37 |
|
38 | | -- description: Implement a backup strategy for Oracle databases to meet data protection and recovery requirements |
| 38 | +- description: Implement Autonomous Recovery Service in Azure for ODAA backup strategy |
39 | 39 | aprlGuid: 0583239a-dfb5-44d4-94db-804bfc8e3bd1 |
40 | 40 | recommendationTypeId: null |
41 | 41 | recommendationControl: DisasterRecovery |
42 | 42 | recommendationImpact: High |
43 | 43 | recommendationResourceType: Microsoft.Subscription/subscriptions |
44 | 44 | recommendationMetadataState: Active |
45 | 45 | longDescription: | |
46 | | - Enable OCI-managed backup to Autonomous Recovery Service in Azure/OCI for data protection. Alternatively, configure self-managed backup to Azure Storage services (Blob, Azure Files, ANF) for long-term backups. RMAN validates database backups for physical corruptions. |
| 46 | + Enable OCI-managed backup to Autonomous Recovery Service in Azure for data protection. |
| 47 | + ARS provides automated, policy-based backups with continuous validation. |
47 | 48 | potentialBenefits: Provide workload data protection. |
48 | 49 | pgVerified: false |
49 | 50 | automationAvailable: no |
|
53 | 54 | url: "https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/scenarios/oracle-iaas/oracle-disaster-recovery-oracle-database-azure" |
54 | 55 |
|
55 | 56 |
|
56 | | -- description: Document and test DR procedure ensure it meets RPO and RTO targets |
57 | | - aprlGuid: a64ea6f4-8c6b-4b76-b152-4e862d19264d |
58 | | - recommendationTypeId: null |
59 | | - recommendationControl: DisasterRecovery |
60 | | - recommendationImpact: High |
61 | | - recommendationResourceType: Microsoft.Subscription/subscriptions |
62 | | - recommendationMetadataState: Active |
63 | | - longDescription: | |
64 | | - Document DR procedures for Oracle Database@Azure and related applications. |
65 | | - Include configuration, failover mechanisms, and recovery steps. Test various failure scenarios to ensure the DR strategy meets RPO/RTO targets and provides seamless failover. |
66 | | - potentialBenefits: Ensures robust DR architecture, meets RPO/RTO |
67 | | - pgVerified: false |
68 | | - automationAvailable: no |
69 | | - tags: [ORACLE] |
70 | | - learnMoreLink: |
71 | | - - name: Business continuity and disaster recovery considerations for Oracle Database@Azure |
72 | | - url: "https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/scenarios/oracle-iaas/oracle-disaster-recovery-oracle-database-azure" |
73 | | - |
74 | | - |
75 | | -- description: Scale up the VM cluster based on the workload requirement |
| 57 | +- description: Monitor critical Oracle Database metrics with defined thresholds and scale accordingly |
76 | 58 | aprlGuid: 2322a597-a6af-4c3e-a1b1-d1b1ddead508 |
77 | 59 | recommendationTypeId: null |
78 | 60 | recommendationControl: Scalability |
|
96 | 78 | aprlGuid: 1bfdf86c-f501-4ad9-99a7-b29b736f34dc |
97 | 79 | recommendationTypeId: null |
98 | 80 | recommendationControl: OtherBestPractices |
99 | | - recommendationImpact: High |
| 81 | + recommendationImpact: Medium |
100 | 82 | recommendationResourceType: Microsoft.Subscription/subscriptions |
101 | 83 | recommendationMetadataState: Active |
102 | 84 | longDescription: | |
|
111 | 93 | url: "https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/scenarios/oracle-iaas/oracle-capacity-planning-oracle-database-azure" |
112 | 94 |
|
113 | 95 |
|
114 | | -- description: Only one ODAA delegated subnet must exist within the VNet |
115 | | - aprlGuid: 76c9136c-642d-4ea3-a4f5-655f28d2ee07 |
116 | | - recommendationTypeId: null |
117 | | - recommendationControl: OtherBestPractices |
118 | | - recommendationImpact: High |
119 | | - recommendationResourceType: Microsoft.Subscription/subscriptions |
120 | | - recommendationMetadataState: Active |
121 | | - longDescription: | |
122 | | - An Azure VNet must have only one ODAA delegated subnet. However other delegated subnets can exist for other services e.g. Azure NetApp Files. |
123 | | - potentialBenefits: Avoid multiple ODAA delegated subnets within a VNet. |
124 | | - pgVerified: false |
125 | | - automationAvailable: no |
126 | | - tags: [ORACLE] |
127 | | - learnMoreLink: |
128 | | - - name: Network Planning for Oracle Database@Azure |
129 | | - url: "https://learn.microsoft.com/en-us/azure/oracle/oracle-db/oracle-database-network-plan#constraints" |
130 | | - |
131 | | -- description: Deploy Data Guard observer in a redundant manner |
| 96 | +- description: Deploy Data Guard observer in different Availability zones for high availability |
132 | 97 | aprlGuid: 768a5b06-41d4-4f10-b544-fbd2f6999af4 |
133 | 98 | recommendationTypeId: null |
134 | 99 | recommendationControl: BusinessContinuity |
135 | | - recommendationImpact: Medium |
| 100 | + recommendationImpact: High |
136 | 101 | recommendationResourceType: Microsoft.Subscription/subscriptions |
137 | 102 | recommendationMetadataState: Active |
138 | 103 | longDescription: | |
139 | | - Deploy Data Guard observer nodes in different AZs and make sure that an observer node will always stay up if anything happens to the Production deployment. |
| 104 | + Deploy Data Guard observer nodes in different AZs and make sure that an observer node will remain available if anything happens to the Production deployment. |
140 | 105 | potentialBenefits: Data Guard observer automates database failover. |
141 | 106 | pgVerified: false |
142 | 107 | automationAvailable: no |
|
145 | 110 | - name: Business continuity and disaster recovery considerations for Oracle Database@Azure |
146 | 111 | url: "https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/scenarios/oracle-iaas/oracle-disaster-recovery-oracle-database-azure" |
147 | 112 |
|
148 | | -- description: When using customer-managed encryption keys with OKV, setup OKV cluster in a redundant manner. |
| 113 | +- description: When using customer-managed encryption keys with Oracle Key Vault, setup Oracle Key Vault cluster in a highly available cluster configuration. |
149 | 114 | aprlGuid: bbe4014f-c49d-475d-9c48-76cb3c190483 |
150 | 115 | recommendationTypeId: null |
151 | 116 | recommendationControl: HighAvailability |
|
179 | 144 | learnMoreLink: |
180 | 145 | - name: Configure Oracle-Managed Infrastructure Maintenance |
181 | 146 | url: "https://docs.oracle.com/en-us/iaas/exadatacloud/doc/exa-conf-oracle-man-infra.html" |
182 | | - |
183 | | -- description: Use infrastructure as code (IaC) for more reliable Oracle Database@Azure deployment |
184 | | - aprlGuid: 5d870898-97d7-437d-9ea9-d8ccced7e6fe |
185 | | - recommendationTypeId: null |
186 | | - recommendationControl: OtherBestPractices |
187 | | - recommendationImpact: Medium |
188 | | - recommendationResourceType: Microsoft.Subscription/subscriptions |
189 | | - recommendationMetadataState: Active |
190 | | - longDescription: | |
191 | | - Automate the provisioning of Oracle Database@Azure deployment. Use the same deployment to secondary site to minimize risk of human error. |
192 | | - potentialBenefits: Standardize Oracle deployments to minimize human error |
193 | | - pgVerified: false |
194 | | - automationAvailable: no |
195 | | - tags: [ORACLE] |
196 | | - learnMoreLink: |
197 | | - - name: Configure Oracle-Managed Infrastructure Maintenance |
198 | | - url: "https://docs.oracle.com/en-us/iaas/exadatacloud/doc/exa-conf-oracle-man-infra.html" |
0 commit comments