Short answer: Oracle DR licensing cloud rules require you to fully license any standby that has Oracle software installed and ready to run. Oracle's 10-day failover exemption only applies when nodes share a storage array — which cross-region AWS, Azure, and OCI standbys do not. Only a cold standby with no installed Oracle binaries can avoid licensing.
Key Takeaways
- Oracle licenses installed-and-running capability, not active use — a warm or active standby in the cloud must be fully licensed for the processors or NUP it can access.
- The 10-day failover rule allows failover to an unlicensed node for up to 10 separate 24-hour periods per year, but only when nodes share a storage array — a condition cross-region cloud DR rarely meets.
- Basic Data Guard is included with Enterprise Edition, but both primary and standby must be fully EE-licensed; Active Data Guard is a separately priced option.
- On AWS and Azure, standby vCPUs count under the Authorized Cloud Environment policy; on OCI, standbys count by OCPU/ECPU and may use BYOL.
- A cold standby with no Oracle software installed is the only configuration that can avoid licensing — it must be genuinely uninstalled, not merely powered off.
- In our engagements, roughly 1 in 3 cloud DR designs are over-licensed or non-compliant on first review, typically because a "passive" standby was treated as free (Oracle Licensing Experts, 2026).
How Does Oracle License Disaster Recovery in the Cloud?
Oracle licenses software based on where it is installed and/or running, not on whether it is actively serving users. This is the single principle that governs all disaster recovery licensing: a standby database that has Oracle binaries installed and can be started is licensable, even if it sits idle for 364 days a year. Disaster recovery (DR) is the practice of maintaining a secondary copy of a database in a separate location so that service can resume after a primary-site failure — and in the cloud that secondary copy is almost always a running, licensable instance.
Across AWS, Azure, and OCI the counting metric differs, but the principle does not. On AWS and Azure, Oracle counts the standby's virtual CPUs under its Authorized Cloud Environment policy; on OCI, it counts OCPUs or ECPUs and permits BYOL. In every case, the question Oracle's audit team asks is the same: is Oracle software installed on that standby, and can it run? If yes, it needs a license. The expensive misunderstanding is treating "passive" or "DR-only" as a synonym for "unlicensed."
Oracle sales will rarely volunteer that your DR standby is fully licensable — but Oracle's audit team treats it as a primary finding. We have seen customers carry a "free" warm standby for years, then face a back-license claim covering every processor on that standby plus four years of backdated 22% support. The standby was never free; it was simply uncounted until the audit. Design DR knowing the standby is licensable, and the audit holds no surprises.
What Is Oracle's 10-Day Failover Rule and Does It Apply in the Cloud?
The 10-day rule is Oracle's limited failover allowance: a fully licensed primary may fail over to an unlicensed spare node for up to ten separate 24-hour periods within a single calendar year, without licensing the spare. The critical condition, stated in Oracle's licensing policy, is that the nodes must be part of a cluster sharing a single storage array or disk subsystem. The allowance does not roll over, and once exhausted the failover node must be licensed.
In public-cloud DR this rule usually evaporates. Cross-region and cross-cloud standbys replicate data over the network; they do not share a physical storage array with the primary, so the precondition for the 10-day rule is not met. A standby in a different AWS region, a different Azure region, or on OCI cannot rely on the 10-day allowance. The rule may apply only where genuine shared storage exists within a single environment — a narrow case in cloud architecture. Assuming the 10-day rule covers a cross-region cloud standby is one of the most common and most costly DR licensing errors we challenge.
When Must a Cloud Standby Server Be Fully Licensed?
A cloud standby must be fully licensed whenever Oracle software is installed on it and the instance can run that software — which describes nearly every practical DR design. A warm standby (installed, mounted, continuously applying redo) and a hot or active standby (installed and open for read traffic) both require full licensing for every processor or Named User Plus they can use. Only a true cold standby — no Oracle binaries installed, restored from backup only at disaster time — can avoid licensing.
The cold-standby exemption is narrower than teams expect. Powering off an instance that already has Oracle installed does not make it a cold standby; the binaries are still installed, so it remains licensable. To genuinely qualify, the DR environment must hold no installed Oracle software until a disaster is declared, at which point licenses are mobilized to the recovery instance. This is operationally demanding, which is why most enterprises accept that their cloud standby is licensed and instead focus on right-sizing it and lowering the support cost.
| Standby type | Oracle software installed? | Licensing required? | 10-day rule available? | Typical cloud use |
|---|---|---|---|---|
| Cold standby | No (restored at disaster) | No, until activated | N/A | Lowest cost, highest RTO |
| Warm standby (Data Guard) | Yes, applying redo | Yes, full standby | Only if shared storage | Most common cross-region DR |
| Active / hot standby | Yes, open read-only | Yes + Active Data Guard option | No | Read offload + DR |
| Clustered failover node (shared storage) | Yes, idle | Up to 10 days unlicensed | Yes | Rare in public cloud |
Is Oracle Data Guard Free for Cloud DR?
Data Guard is Oracle's built-in replication technology that ships a redo stream from a primary database to one or more standby databases. Basic Data Guard is included at no extra license cost with Oracle Database Enterprise Edition — but "included" refers only to the feature, not to the standby server. Both the primary and the standby must be fully licensed for Enterprise Edition, so a Data Guard DR pair in the cloud is two fully licensed EE deployments, not one.
Active Data Guard is a separately licensed Enterprise Edition option that lets the standby be open for read-only queries or fast incremental backups while it applies redo. The moment a standby is opened read-only, Active Data Guard licensing is triggered — a frequent and expensive surprise when a team enables read offload on a DR replica without realizing it converts a base EE standby into an Active Data Guard one. For the full set of EE options and how Oracle counts them, see our Oracle Database licensing guide.
How Does DR Licensing Differ Across AWS, Azure, and OCI?
The licensing principle is constant, but the counting metric changes by platform. On AWS and Azure, Oracle's Authorized Cloud Environment policy counts the standby's vCPUs, treating 2 vCPUs as a licensable processor where hyper-threading is on (and the Core Factor Table is excluded). On OCI, the standby is counted by OCPU or ECPU, and customers can apply BYOL to cover the standby with licenses they already own — often the most cost-effective route for an OCI-based DR target.
Cross-cloud DR — primary on Azure, standby on OCI, for example — is licensable on both ends under each platform's metric, and the 10-day rule never applies because storage is not shared. The practical optimization is to size the standby to the minimum capacity that meets your recovery time objective, place it on the platform where BYOL or commercial terms are most favorable, and document the configuration so it can be defended. Our Oracle multi-cloud licensing guide covers the cross-platform counting in depth, and the Oracle Cloud licensing guide is the full pillar reference.
Designing DR across AWS, Azure, or OCI?
Our Oracle Cloud advisory service right-sizes standby capacity, confirms whether any failover exemption applies, and documents a DR design that survives an Oracle audit.
How Do You Cut the Cost of Oracle DR Licensing?
Because the standby is almost always licensable, the savings come from three levers. First, right-size the standby: size it to the minimum capacity that meets your recovery time objective rather than mirroring the primary, since a DR target rarely needs full production horsepower until it is actually serving traffic. Second, place the standby strategically, using OCI BYOL or favorable commercial terms where they reduce the effective per-processor cost. Third, cut the support cost on the licenses you hold.
That third lever is often the largest. Every DR license carries Oracle's 22% annual support fee, and moving the licenses that cover DR to third-party support can save 50–70% of that recurring cost while still maintaining the entitlement. Our Oracle support cost reduction service and third-party support advisory model the savings against your specific DR footprint. Across our engagements, right-sizing plus support reduction typically removes 30–40% of total Oracle DR cost without weakening resilience (Oracle Licensing Experts, 2026). See how this played out in our client case studies.
Frequently Asked Questions: Oracle DR Licensing in the Cloud
How does Oracle's 10-day failover rule work in the cloud?
Oracle's 10-day rule lets a fully licensed primary fail over to an unlicensed standby for up to 10 separate 24-hour periods per calendar year, only when the nodes share a storage array. The allowance does not reset and the standby must otherwise be idle. Cloud standbys rarely share storage, so the rule usually does not apply in AWS, Azure, or OCI.
Do I need to license an Oracle standby server in the cloud?
Yes, in almost all cloud DR designs. Any standby with Oracle software installed and ready to run must be fully licensed for the processors or NUP it can use, because Oracle licenses installed-and-running capability, not just active use. A cold standby with no installed binaries is the only configuration that may avoid licensing.
Is Oracle Data Guard free to use for disaster recovery?
Basic Data Guard is included with Enterprise Edition, but both the primary and the standby must be fully EE-licensed. Active Data Guard, which allows read access or fast incremental backups on the standby, is a separately licensed option on top of Enterprise Edition.
Does the 10-day rule apply across AWS, Azure, and OCI?
The 10-day rule requires the failover node to share a storage array with the primary. Public-cloud standbys in a different region or cloud do not share storage, so the rule generally cannot be claimed for cross-region or cross-cloud DR. It may apply within a single cloud only where shared storage genuinely exists.
How is Oracle DR licensed on OCI versus AWS or Azure?
On AWS and Azure, Oracle counts standby vCPUs under its Authorized Cloud Environment policy. On OCI, standby instances are counted by OCPU or ECPU and may use BYOL. In all three, a running standby requires full licensing unless it qualifies as a cold, uninstalled failover environment.
Can third-party support cover my Oracle DR environment?
Third-party support can maintain the licenses you already own, including those covering DR standbys, and saves roughly 50 to 70 percent of Oracle's 22 percent annual support fee. It does not change the underlying license requirement for the standby, but it lowers the recurring cost of holding those DR licenses.