Disaster Recovery vs Migrate
Yorigu Disaster Recovery is for ongoing protection, validation, failover, and failback. Yorigu Migrate is for controlled movement, dry runs, cutover, validation, and rollback planning.
Product Family
Yorigu Products
Yorigu products are organized around Disaster Recovery and Migration objectives, with target-specific delivery and workload-aware packaging.
Yorigu Disaster Recovery for OCI
Recovery lifecycle automation for OCI
Protect Machine and DB System workloads with synchronization, validation, failover, and failback workflows for Oracle Cloud Infrastructure.
SyncFailoverFailback
Yorigu Migrate for OCI
Controlled workload migration to OCI
Move Machine and DB System workloads to Oracle Cloud Infrastructure with dry-run, cutover, validation, and rollback planning.
AssessCutoverRollback
Yorigu Disaster Recovery for Proxmox
Recovery lifecycle automation for Proxmox VE
Protect Machine and DB System workloads with synchronization, validation, failover, and failback workflows for Proxmox VE environments.
SyncFailoverFailback
Yorigu Migrate for Proxmox
Controlled workload migration to Proxmox VE
Move Machine and DB System workloads to Proxmox VE with dry-run, cutover, validation, and rollback planning.
AssessCutoverRollback
Yorigu Disaster Recovery for OLVM
Recovery lifecycle automation for Oracle Linux Virtualization Manager environments
Protect physical servers, virtual machines, and DB System workloads to Oracle Linux Virtualization Manager with target-specific validation, failover readiness, and failback planning.
SyncFailoverFailback
Yorigu Migrate for OLVM
Controlled workload migration to Oracle Linux Virtualization Manager
Move physical, virtual, and database workloads to OLVM with staged preparation, cutover validation, rollback planning, and operational handoff.
AssessCutoverRollback
Compare
How to Choose
OCI vs Proxmox
OCI and Proxmox are separate target-specific deliveries. Choose the product that matches the target environment rather than treating both targets as one installation model.
Machine-Only vs Machine + DB System
Machine-only packaging is available when database-aware workflows are not required. Machine + DB System packaging includes physical and virtual machine coverage.
Licensing
Product and License Model
A DB System is one source database deployment: a standalone server, a RAC cluster across hosts, or a single server hosting many databases, counted as one.
Product
Package
Coverage
Methodology
OCI
Yorigu Disaster Recovery for OCI
Machine-only
Physical and virtual machine scope
Agentless recovery coverage for physical servers and virtual machines protected toward Oracle Cloud Infrastructure.
Continuous protection lifecycle with sync, automated validation, failover readiness, and failback preparation for OCI.
OCI
Yorigu Disaster Recovery for OCI
Machine + DB System
Machine coverage plus database-aware workflow coverage
Includes machine coverage and adds database-aware visibility for mission-critical source DB Systems protected toward OCI.
Database consistency, validation state, recovery readiness, and failback preparation are tracked in the same operational workflow.
OCI
Yorigu Migrate for OCI
Machine-only
Physical and virtual machine scope
Agentless migration coverage for physical servers and virtual machines moving to Oracle Cloud Infrastructure.
Migration scope follows assessment, preparation, dry run, cutover, validation, and rollback-window planning.
OCI
Yorigu Migrate for OCI
Machine + DB System
Machine coverage plus database-aware workflow coverage
Includes machine coverage and adds database-aware migration planning for source DB Systems moving to OCI.
Database-aware assessment, dry-run readiness, cutover sequencing, validation, and rollback visibility are part of the migration workflow.
Proxmox
Yorigu Disaster Recovery for Proxmox
Machine-only
Physical and virtual machine scope
Agentless recovery coverage for physical servers and virtual machines protected toward Proxmox VE.
Private-cloud DR lifecycle with sync, validation, failover readiness, and failback preparation for Proxmox.
Proxmox
Yorigu Disaster Recovery for Proxmox
Machine + DB System
Machine coverage plus database-aware workflow coverage
Includes machine coverage and adds database-aware visibility for mission-critical DB systems protected toward Proxmox.
Database alignment, validation state, failover readiness, and failback preparation remain visible with the machine-level workflow.
Proxmox
Yorigu Migrate for Proxmox
Machine-only
Physical and virtual machine scope
Agentless migration coverage for physical servers and virtual machines moving to Proxmox VE.
Migration scope follows assessment, preparation, dry run, cutover, validation, and rollback-window planning for Proxmox.
Proxmox
Yorigu Migrate for Proxmox
Machine + DB System
Machine coverage plus database-aware workflow coverage
Includes machine coverage and adds database-aware migration planning for DB systems moving to Proxmox.
Database-aware wave planning, cutover readiness, validation, and rollback visibility are handled alongside machine migration.
OLVM
Yorigu Disaster Recovery for OLVM
Machine-only
Physical and virtual machine scope
Agentless recovery coverage for physical servers and virtual machines protected toward Oracle Linux Virtualization Manager.
On-premises DR lifecycle with sync, validation, failover readiness, and failback preparation for OLVM.
OLVM
Yorigu Disaster Recovery for OLVM
Machine + DB System
Machine coverage plus database-aware workflow coverage
Includes machine coverage and adds database-aware visibility for mission-critical DB Systems protected toward OLVM.
Database alignment, validation state, failover readiness, failback preparation, and placement review remain visible with the machine-level workflow.
OLVM
Yorigu Migrate for OLVM
Machine-only
Physical and virtual machine scope
Agentless migration coverage for physical servers and virtual machines moving to Oracle Linux Virtualization Manager.
Migration scope follows assessment, preparation, dry run, cutover, validation, and rollback-window planning for OLVM.
OLVM
Yorigu Migrate for OLVM
Machine + DB System
Machine coverage plus database-aware workflow coverage
Includes machine coverage and adds database-aware migration planning for DB Systems moving to OLVM.
Database-aware assessment, cutover readiness, validation, rollback visibility, and governed target placement are handled alongside machine migration.
Includes Machine Coverage
Customers selecting Machine + DB System coverage receive physical and virtual machine replication or migration as part of the same scope. Machine-only does not need to be purchased separately.
DB System Counting
DB System capacity is counted by DB System, not by individual database. A server hosting many small databases is one DB System for scope planning.
Scoped Commercially
Infrastructure costs, cloud usage, and deployment services are quoted in your engagement proposal.
Application Plans Are Separate
Application Plans are enabled only when the signed license grants the application-plans capability. They are not implied by Machine-only or Machine + DB System scope.
Next Step
POC License
Qualified customers can request a POC License after an initial scope discussion. The POC scope is defined around operational requirements, access readiness, and validation objectives.