Oracle Cloud Infrastructure
Cloud target platform for Disaster Recovery and Migration deployments, with OCI-specific provisioning, validation, and cutover planning.
Platform Compatibility
Platform-Independent Workload Coverage
In Yorigu architecture, the product boundary is the workload, not the infrastructure it currently runs on. Source environment, operating system, and database engine coverage are handled separately from target delivery models, enabling recovery and migration planning without vendor lock-in.
Source Workloads
Source workloads can be Physical Servers, Virtual Machines, or DB Systems running across On-Premises, Cloud, hosted, or virtualized environments. Yorigu evaluates coverage at the workload and operating system level instead of treating the source location as the product boundary.
Physical ServersVirtual MachinesDB SystemsVMware vSphere / ESXiWindows Server 2008 R2 - 2025Oracle Linux 7 / 8 / 9Red Hat Enterprise Linux 7 / 8 / 9SUSE Linux Enterprise Server 12 / 15Ubuntu Server 20.04 / 22.04 / 24.04Debian 10 / 11 / 12 / 13
Common Use Cases
Common source and target combinations
VMware vSphere / ESXi → Oracle Cloud Infrastructure
VMware to OCI Disaster Recovery
Disaster Recovery · AgentlessVMware vSphere / ESXi → Oracle Cloud Infrastructure
VMware to OCI Migration
Migration · AgentlessPhysical Servers → Oracle Cloud Infrastructure
Physical to OCI Disaster Recovery
Disaster Recovery · AgentlessPhysical Servers → Oracle Cloud Infrastructure
Physical to OCI Migration
Migration · AgentlessVMware vSphere / ESXi → Proxmox VE
VMware to Proxmox Disaster Recovery
Disaster Recovery · AgentlessVMware vSphere / ESXi → Proxmox VE
VMware to Proxmox Migration
Migration · AgentlessPhysical Servers → Proxmox VE
Physical to Proxmox Disaster Recovery
Disaster Recovery · AgentlessPhysical Servers → Proxmox VE
Physical to Proxmox Migration
Migration · AgentlessVMware vSphere / ESXi → Oracle Linux Virtualization Manager
VMware to OLVM Disaster Recovery
Disaster Recovery · AgentlessVMware vSphere / ESXi → Oracle Linux Virtualization Manager
VMware to OLVM Migration
Migration · AgentlessPhysical Servers → Oracle Linux Virtualization Manager
Physical to OLVM Disaster Recovery
Disaster Recovery · AgentlessPhysical Servers → Oracle Linux Virtualization Manager
Physical to OLVM Migration
Migration · Agentless
Target Delivery Models
Target delivery is platform-specific. OCI, Proxmox VE, and OLVM each keep their own deployment, validation, and rollout assumptions.
Target selection also determines data residency. OCI keeps workloads in the chosen OCI region, and Proxmox VE keeps them on infrastructure the organization controls.
Proxmox VE
On-Premises and Virtualized Infrastructure target for Disaster Recovery and Migration deployments, with Proxmox VE-specific delivery and validation.
Oracle Linux Virtualization Manager
On-premises target for Disaster Recovery and Migration where Oracle Linux KVM, OLVM management, Oracle Database placement, and Oracle-documented hard partitioning planning need to stay aligned.
Database-Aware Workflows
Database-Aware workflows add consistency, validation, cutover readiness, and recovery readiness for supported DB Systems without treating databases as generic machines.
Oracle DatabaseMicrosoft SQL ServerPostgreSQLMySQLMongoDBSAP HANA
Next Step
Need a Platform Not Listed?
Reach out to discuss compatibility for environments or database deployments outside the lists above.