A disaster can be any event that puts applications at risk, for example failures caused by natural disasters. In regions with cross-region disaster recovery (DR) enabled, identity domains have built-in cross-region DR to minimize data loss. Data for a region is replicated to a nearby region in the event of a disaster. If an entire OCI region becomes unavailable, traffic is routed to the disaster recovery region to speed service recovery and retain as much data as possible. Oracle pairs regions with disaster recovery (DR) regions for you.
If a region outage occurs, the identity domain will experience a brief outage and then recover. After recovered to the DR region:
Users in the identity domain are authenticated and authorized as usual.
Identity domain URLs don't change. No changes are needed for any applications.
Failed-over identity domains don't replicate to replicated regions.
Identity domains replicated to other regions might not be in sync with the DR region. For example, any changes to users, groups, and domain settings might not be reflected in the DR region. Inconsistencies are resolved when the identity domain fails back.
Accessing the DR Region
Use these steps to confirm that the network can reach the DR region.
Add those public IP addresses to your firewalls to allow traffic from that DR
region.
Note
For complete disaster recovery functionality, we recommend subscribing a tenancy to its DR region pairing. Replicate the tenancy's domains to the DR region. This all IAM principal-based authentication while the home region is down.
If a region outage occurs, OCI might initiate a failover of that region's identity domains (and IDCS stripes) to a failover region which restores access to those identity domains (and IDCS stripes) in a read-only access mode. Check the outage information for when the region-outage state is enabled & disabled.
In read-only access mode:
Resources can't be updated. No updates to any identity domain (or IDCS stripe) resources are allowed. For example, users can't update or delete users, applications, groups, or domain settings. Users have read permissions to all resources.
Users can't change their passwords. If a user is in the force password reset state, they
can't reset their password and don't have access until the region outage has been
mitigated.
Users with multifactor authentication can sign-in while the identity domain is in read-only mode.
Applications using the identity domain can authenticate and authorize. For example, a
custom application can authenticate and authorize calls using the identity domain while in
read-only mode.