The image shows the architecture for disaster recovery from OCI to Compute Cloud@Customer showing a Passive or Standby On-Premises site on the left and an active or production OCI Region on the right. Internet traffic is routed through a DNS to and from both the active and passive sites.

On-Premises passive or standby site

This on-premises site hosts Compute Cloud@Customer with multiple Windows Linux Containers each including Web/App and Block Storage.

The site also hosts a Standby Oracle Database, two OL VMs, and NFSv4.

OCI Region active or production site

This on-premises site hosts Rackware DR Plan with Web/App VMs and Mounted Block Storage.

The site also hosts a Primary Oracle Database, two OL VM, and OCI Object Storage. The Rackware RMM Server connects to origins server using SSH and TCP 22 and interacts using the Cloud API. The user interacts using the Jump Server which uses an SSH or GUI to connect with RMM.

The on-premises standby site has a CPE and connects using site-to-site VPN to the OCI Region with a DRG. The two sites Block Storage and Mounted Block Storage are connected using Rackware Automation of DR Failover or Failback (Agent based). A two-way connector arrow shows the connection between the Block Storage in the passive site and Mounted Block storage in the active site.

Oracle Data Guard replication is depicted with a two-sided arrow pointing to the OL VM in each site. The OL VM hosts the Oracle Databases on the primary and standby sites and includes OCI Object Storage in the active or production site.