Yorigu
Products
Yorigu Disaster Recovery for OCI Yorigu Disaster Recovery for Proxmox Yorigu Migrate for OCI Yorigu Migrate for Proxmox DB System Workloads Licensing
Solutions
All Use CasesVMware to OCI Disaster RecoveryVMware to OCI MigrationVMware to Proxmox Disaster RecoveryVMware to Proxmox MigrationPhysical to OCI Disaster RecoveryPhysical to OCI MigrationPhysical to Proxmox Disaster RecoveryPhysical to Proxmox MigrationDB-Aware OCI MigrationDB-Aware OCI Disaster RecoveryDB-Aware Proxmox MigrationDB-Aware Proxmox Disaster Recovery
Platforms How It Works About Contact Portal

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.

Source coverage is OS-level and confirmed during POC planning; environments beyond the listed production paths are scoped on request.

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

These use cases are relevant when planning starts from the current estate, the target platform, and the recovery or migration objective.

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 · Agentless

Target Delivery Models

Target delivery is platform-specific. OCI and Proxmox VE 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.

Cloud OCI

Oracle Cloud Infrastructure

Cloud target platform for Disaster Recovery and Migration deployments, with OCI-specific provisioning, validation, and cutover planning.

On-Premises / Virtualized Proxmox VE

Proxmox VE

On-Premises and Virtualized Infrastructure target for Disaster Recovery and Migration deployments, with Proxmox VE-specific delivery and validation.

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 ServerPostgreSQLMySQLSAP HANA

Next Step

Need a Platform Not Listed?

Reach out to discuss compatibility for environments or database deployments outside the lists above.

Discuss Compatibility