User Responsibilities

Because Oracle handles nearly all disaster recovery management tasks, your responsibilities as an administer are kept to a minimum. You only have several major responsibilities in an Oracle-managed disaster recovery environment:

Task	Description	See..
Subscribe to and configure the secondary region	Subscribe to the secondary region to ensure that secondary instance creation is successful, add a policy to manage integration instances, and configure the necessary policies for any default or defined tags you are using.	Perform Preinstallation Tasks
Install primary and secondary instances	Select the Enable disaster recovery toggle when installing an instance in the Oracle Cloud Infrastructure Console. This action creates primary and secondary instances in separate, predetermined regions. Data synchronization between the two instances is automatically configured and occurs in near real time.	Install and Configure Oracle Integration for Disaster Recovery
Perform prerequisites prior to failover	Review the following prerequisites to determine if they apply to your setup: If your connectivity agent is installed in an Oracle Cloud Infrastructure Compute instance that fails, you must have a plan in place that allows for a quick recovery of the connectivity agent. If you are using your own email tenancy, you must manually maintain your email notification details in your primary and secondary instances. If you are using File Server, connections to it must use the port and hostname, rather than the port and IP address. If you are using private endpoints, you must manually enable this feature on your primary and secondary instances.	Perform Failover Prerequisite Tasks
Fail over and fail back between instances in different regions	Two types of failover are supported: If your primary instance is unreachable, you click Start Failover in the Oracle Cloud Infrastructure Console of the secondary instance to fail over to that instance. Once the original primary instance is restored, you can then fail back to that instance. If you want to perform a planned migration between instances periodically, you click Start Failover in the Oracle Cloud Infrastructure Console of either the primary or secondary instance to fail over to the secondary instance.	Fail Over to the Other Instance
Configure email notification settings after failover (if using your own email tenancy)	After failover occurs, you must configure email notification settings on the Notifications page of the new primary instance.	Configure Email Notification Settings After Failover

Understand Failover Behavior

Bidirectional data synchronization (replication) is regularly performed in near real time between the two instances to reduce the chance of data loss after failover.
Failover is a one instance-to-one instance replication, meaning you can only fail over to a second instance. You cannot fail over to multiple instances.
When a failover is performed, the secondary instance takes over the responsibility of providing all features of the primary instance.
The primary instance goes into standby mode and becomes a passive listener when the secondary instance becomes active.
All traffic that was originally sent to the initial primary instance is forwarded to the new primary instance.
The life cycle operations in the standby instance are disabled in the Oracle Cloud Infrastructure Console with the exception of performing a failover.
There are no changes in OAuth credentials after failover.
Only design-time metadata is synchronized. Runtime tracking data such as that shown in the activity stream, Instance page, and other observability pages is not synchronized with the secondary instance.
You log in to primary and secondary instances with a global URL that does not include a region name.
If you delete the primary instance, the secondary instance is also deleted.
If you start and stop the primary instance, this has no impact on the secondary instance, which simply remains a passive listener.