|
3 | 3 | recommendationTypeId: null |
4 | 4 | recommendationControl: BusinessContinuity |
5 | 5 | recommendationImpact: High |
6 | | - recommendationResourceType: Specialized.Workload/oracle |
| 6 | + recommendationResourceType: Microsoft.Subscription/subscriptions |
7 | 7 | recommendationMetadataState: Active |
8 | 8 | longDescription: |
9 | 9 | Define a BCDR strategy based on workload RPO/RTO. |
|
22 | 22 | recommendationTypeId: null |
23 | 23 | recommendationControl: DisasterRecovery |
24 | 24 | recommendationImpact: High |
25 | | - recommendationResourceType: Specialized.Workload/oracle |
| 25 | + recommendationResourceType: Microsoft.Subscription/subscriptions |
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. |
|
40 | 40 | recommendationTypeId: null |
41 | 41 | recommendationControl: DisasterRecovery |
42 | 42 | recommendationImpact: High |
43 | | - recommendationResourceType: Specialized.Workload/oracle |
| 43 | + recommendationResourceType: Microsoft.Subscription/subscriptions |
44 | 44 | recommendationMetadataState: Active |
45 | 45 | longDescription: | |
46 | 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. |
|
58 | 58 | recommendationTypeId: null |
59 | 59 | recommendationControl: DisasterRecovery |
60 | 60 | recommendationImpact: High |
61 | | - recommendationResourceType: Specialized.Workload/oracle |
| 61 | + recommendationResourceType: Microsoft.Subscription/subscriptions |
62 | 62 | recommendationMetadataState: Active |
63 | 63 | longDescription: | |
64 | 64 | Document DR procedures for Oracle Database@Azure and related applications. |
|
77 | 77 | recommendationTypeId: null |
78 | 78 | recommendationControl: Scalability |
79 | 79 | recommendationImpact: Medium |
80 | | - recommendationResourceType: Specialized.Workload/oracle |
| 80 | + recommendationResourceType: Microsoft.Subscription/subscriptions |
81 | 81 | recommendationMetadataState: Active |
82 | 82 | longDescription: | |
83 | 83 | Monitor database metrics such as CPU utilization and memory usage with Azure Monitor, setting alerts for scaling decisions. |
|
97 | 97 | recommendationTypeId: null |
98 | 98 | recommendationControl: OtherBestPractices |
99 | 99 | recommendationImpact: High |
100 | | - recommendationResourceType: Specialized.Workload/oracle |
| 100 | + recommendationResourceType: Microsoft.Subscription/subscriptions |
101 | 101 | recommendationMetadataState: Active |
102 | 102 | longDescription: | |
103 | 103 | Design an IP addressing scheme considering current and future Oracle workload needs to prevent conflicts and ensure availability. |
|
116 | 116 | recommendationTypeId: null |
117 | 117 | recommendationControl: OtherBestPractices |
118 | 118 | recommendationImpact: High |
119 | | - recommendationResourceType: Specialized.Workload/oracle |
| 119 | + recommendationResourceType: Microsoft.Subscription/subscriptions |
120 | 120 | recommendationMetadataState: Active |
121 | 121 | longDescription: | |
122 | 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. |
|
133 | 133 | recommendationTypeId: null |
134 | 134 | recommendationControl: BusinessContinuity |
135 | 135 | recommendationImpact: Medium |
136 | | - recommendationResourceType: Specialized.Workload/oracle |
| 136 | + recommendationResourceType: Microsoft.Subscription/subscriptions |
137 | 137 | recommendationMetadataState: Active |
138 | 138 | longDescription: | |
139 | 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. |
|
150 | 150 | recommendationTypeId: null |
151 | 151 | recommendationControl: HighAvailability |
152 | 152 | recommendationImpact: High |
153 | | - recommendationResourceType: Specialized.Workload/oracle |
| 153 | + recommendationResourceType: Microsoft.Subscription/subscriptions |
154 | 154 | recommendationMetadataState: Active |
155 | 155 | longDescription: | |
156 | 156 | Provide redundancy for VMs used as OKV, note that this is only relevant if customer is using own keys and only if OCI vault is not used. A minimum 4-node OKV cluster deployment is recommended across two AZs or regions, aligned with the BCDR architecture. |
|
167 | 167 | recommendationTypeId: null |
168 | 168 | recommendationControl: OtherBestPractices |
169 | 169 | recommendationImpact: High |
170 | | - recommendationResourceType: Specialized.Workload/oracle |
| 170 | + recommendationResourceType: Microsoft.Subscription/subscriptions |
171 | 171 | recommendationMetadataState: Active |
172 | 172 | longDescription: | |
173 | 173 | Non-rolling maintenance incurs a downtime. |
|
185 | 185 | recommendationTypeId: null |
186 | 186 | recommendationControl: OtherBestPractices |
187 | 187 | recommendationImpact: Medium |
188 | | - recommendationResourceType: Specialized.Workload/oracle |
| 188 | + recommendationResourceType: Microsoft.Subscription/subscriptions |
189 | 189 | recommendationMetadataState: Active |
190 | 190 | longDescription: | |
191 | 191 | Automate the provisioning of Oracle Database@Azure deployment. Use the same deployment to secondary site to minimize risk of human error. |
|
0 commit comments