This image shows a topology that includes three sites: an on-premises site, a 3rd party cloud site, and an OCI region.

The on-premises site is labeled as a source, and contains:

• A bare metal machine with a ZDM agent installed.
• A virtual machine with a ZDM agent installed.
• A ZDM instance, named ZDM1-A, which receives information from the ZDM agents.
• Local storage that the ZDM instance uses to store backup images, which include the OS, applications, and data from other machines.
• A customer premises equipment (CPE), which controls the flow of information from the on-premises site to the OCI region.
• Users.

The third party cloud site is labeled as a source, and could be an Azure cloud, an AWS cloud, or a Google Cloud. It contains:

• A bare metal machine with a ZDM agent installed.
• A virtual machine with a ZDM agent installed.
• A ZDM instance, named ZDM3-B, which receives information from the ZDM agents.
• Local storage that the ZDM instance uses to store backup images, which include the OS, applications, and data from other machines.
• Users.

The OCI region is labeled as the target, and contains:

• Bastion Service.
• Three availability domains.
• A group of OCI Services, which includes: Policies, OCI IAM, Auditing, Monitoring, and Logging.
• An immutable incremental backup and long-term repository, which includes: an object storage bucket and two backup buckets.
• A VCN.

The VCN has the following features:

• A dynamic routing gateway, which receives traffic from the on-premises site.
• An internet gateway, which receives traffic from the third party cloud site.
• A service gateway, which writes to the long-term repository.
• Three subnets, which include security lists and route tables.

The first availability domain is empty in all subnets.

The second availability domain is used to replicate data from the on-premises site, and contains:

• A public load balancer in subnet 1.
• A ZDM instance (ZDM2-A) in subnet 2.
• Two sets of block storage in subnet 2, which are used by the ZDM instance.
• A target virtual machine in subnet 3, with ZDM agent attached.
• A target bare metal machine in subnet 3, with a ZDM agent attached.

Data from the on-premises site flows into the dynamic routing gateway, then to the load balancer. ZDM2-A, which is paired with ZDM1-A in the on-premises site, receives the data and uses the available block storage to backup the two applications from the on-premises site. It also uses the service gateway to store the backups in the long-term repository. ZMD2-A can then recover those images at any time, and create the target machines in subnet3.

The third availability domain is used to replicate data from the third party cloud site, and contains:

• A ZDM instance (ZDM4-B) in subnet 2.
• Two sets of block storage in subnet 2, which are used by the ZDM instance.
• A target virtual machine in subnet 3, with ZDM agent attached.
• A target bare metal machine in subnet 3, with a ZDM agent attached.

Data from the third party cloud site flows into the internet gateway, then to the load balancer. ZDM4-B, which is paired with ZDM3-B in the third party cloud site, receives the data and uses the available block storage to backup the two applications from the on-premises site. It also uses the service gateway to store the backups in the long-term repository. ZMD2-A can then recover those images at any time, and create the target machines in subnet3.