|
11 | 11 | Use SYNC for zero data loss or ASYNC when performance is constrained. |
12 | 12 | potentialBenefits: Ensure business continuity in case of zonal failure. |
13 | 13 | pgVerified: false |
14 | | - automationAvailable: no |
| 14 | + automationAvailable: false |
15 | 15 | tags: [ORACLE] |
16 | 16 | learnMoreLink: |
17 | 17 | - name: Business continuity and disaster recovery considerations for Oracle Database@Azure |
|
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 | 29 | potentialBenefits: The cloud MAA architecture achieves data protection and DR. |
30 | 30 | pgVerified: false |
31 | | - automationAvailable: no |
| 31 | + automationAvailable: false |
32 | 32 | tags: [ORACLE] |
33 | 33 | learnMoreLink: |
34 | 34 | - name: Business continuity and disaster recovery considerations for Oracle Database@Azure |
|
46 | 46 | ARS provides automated, policy-based backups with continuous validation. |
47 | 47 | potentialBenefits: Provide workload data protection. |
48 | 48 | pgVerified: false |
49 | | - automationAvailable: no |
| 49 | + automationAvailable: false |
50 | 50 | tags: [ORACLE] |
51 | 51 | learnMoreLink: |
52 | 52 | - name: Business continuity and disaster recovery considerations for Oracle Database@Azure |
|
65 | 65 | If needed, scale OCPUs on the VM cluster, if Exa infrastructure capacity allows. |
66 | 66 | potentialBenefits: Meet workload scalability requirements. |
67 | 67 | pgVerified: false |
68 | | - automationAvailable: no |
| 68 | + automationAvailable: false |
69 | 69 | tags: [ORACLE] |
70 | 70 | learnMoreLink: |
71 | 71 | - name: Learn about Manage and monitor Oracle Database@Azure |
|
83 | 83 | Primary, standby, client, and backup subnets should have non-overlapping CIDR ranges for reliable connectivity. |
84 | 84 | potentialBenefits: Avoid conflicts in IP addressing. |
85 | 85 | pgVerified: false |
86 | | - automationAvailable: no |
| 86 | + automationAvailable: false |
87 | 87 | tags: [ORACLE] |
88 | 88 | learnMoreLink: |
89 | 89 | - name: Capacity planning for Oracle Database@Azure |
|
100 | 100 | 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. |
101 | 101 | potentialBenefits: Data Guard observer automates database failover. |
102 | 102 | pgVerified: false |
103 | | - automationAvailable: no |
| 103 | + automationAvailable: false |
104 | 104 | tags: [ORACLE] |
105 | 105 | learnMoreLink: |
106 | 106 | - name: Business continuity and disaster recovery considerations for Oracle Database@Azure |
|
117 | 117 | 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. |
118 | 118 | potentialBenefits: Protect access to keys in case of VM or AZ/region failure. |
119 | 119 | pgVerified: false |
120 | | - automationAvailable: no |
| 120 | + automationAvailable: false |
121 | 121 | tags: [ORACLE] |
122 | 122 | learnMoreLink: |
123 | 123 | - name: Security guidelines for Oracle Database@Azure |
|
135 | 135 | Automatic infrastructure maintenance occurs quarterly, with Oracle notifying you of the date and time weeks in advance. You can modify the scheduled date and time before maintenance starts. |
136 | 136 | potentialBenefits: Keep Oracle workloads up-to-date. |
137 | 137 | pgVerified: false |
138 | | - automationAvailable: no |
| 138 | + automationAvailable: false |
139 | 139 | tags: [ORACLE] |
140 | 140 | learnMoreLink: |
141 | 141 | - name: Configure Oracle-Managed Infrastructure Maintenance |
|
0 commit comments