Troubleshooting

Launching Dr Operations During A Home Region Outage

If the home IAM region is unavailable, OCI Console access to Full Stack DR may be interrupted, preventing DR Plan execution through the console. Initiate recovery using the REST API or another supported interface, such as the OCI CLI, Terraform, or Python; the CLI dr-plan-execution create command accepts an execution-options file specifying whether prechecks and warnings are enabled and whether to run a failover or failover precheck.

Read More: Launching Dr Operations During A Home Region Outage

Resetting Dr Configuration After A Failover

After a successful failover, manually clean up the former primary DR protection group and reverse member configurations before subsequent switchover or failover operations. Confirm the former primary is a standby with an Active state, then refresh and verify all DR plans. Tasks vary by resource: reverse replication for volume groups, file systems, and buckets; avoid terminating removed buckets; remove and terminate applicable compute resources and storage; reconfigure non-moving instance attachments and mounts; reinstate databases through Data Guard; update load balancer backend sets; and remove the brie namespace and DR-managed namespaces from OKE clusters along with their associated resources.

Read More: Resetting Dr Configuration After A Failover

Updating Backend Server Ip Addresses In Oci Load Balancer Backend Sets After Dr Operation

After a switchover, failover, or start drill, load balancers may fail to route traffic to newly launched backend resources in the new primary region. Check the health checks for every DR-managed load balancer, and if checks fail, update the backend server IP addresses in the affected backend sets.

Read More: Updating Backend Server Ip Addresses In Oci Load Balancer Backend Sets After Dr Operation