Data Stays in Your Environment
Yorigu is deployed into the customer-controlled environment. Workloads are recovered and migrated into the selected OCI region or Proxmox VE environment, so data remains within that boundary.
Disaster Recovery and Migration to Cloud or On-Premises
Yorigu protects and moves VMware, physical, and DB System workloads to Oracle Cloud Infrastructure, Proxmox VE, or Oracle Linux Virtualization Manager. Disaster Recovery targets stay powered off until needed, while validation keeps recovery readiness evidence-backed. Database workflows aim for consistent recovery, not generic machine copies.
Oracle Linux
RHEL
SLES
Ubuntu
Debian
Windows Server
Oracle Cloud
Proxmox VE
Oracle Linux Virtualization
Recovery
Application Plans
tiered · gated · evidenced
Databases
Consistent
database-consistent recovery
Standby
Cold Standby
storage-led, not 24/7 compute
Product Family
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
Data Control
Data Sovereignty and Control
You Choose the Target Boundary
Recovery and migration run into the Cloud or On-Premises target the organization selects, so where data lands is a customer decision rather than a fixed vendor destination.
Smaller Change Surface
No persistent Yorigu software runs on production source systems, which keeps the privileged footprint to govern and audit smaller.
Why Yorigu
What Sets Yorigu Apart
Powered-Off Standby Targets
Standby recovery targets stay powered off until a recovery event. This removes the need for continuously running duplicate compute and reduces the ongoing cost of disaster recovery standby.
Cloud or On-Premises Targets
Recover and migrate to OCI or to Proxmox VE. Organizations constrained by cloud policy can replicate to their own physical infrastructure in another location, without purchasing additional VMware licensing. The selected target also defines where the recovered data stays.
Recovery Objectives That Match Priority
Recovery point and recovery time objectives are scoped per workload. Sync frequency, target preparation, validation workflow, and cutover procedure are tuned according to workload priority.
Database-Aware Recovery and Migration
Oracle, SQL Server, PostgreSQL, MySQL, and SAP HANA are handled with consistency and validation awareness, so databases return usable and consistent rather than as generic machine copies.
Automated Validation and AutoHealing
Recovery health is tested automatically on a schedule, with an AutoHealing layer as added protection, so readiness is evidence-backed rather than assumed.
Failback Included
Returning to the original environment is part of the same product and lifecycle, with no separate license and no disconnected reverse tooling.
Beyond VM protection
From machines to data to application evidence
DB Systems
Near-real-time or real-time data protection, consistency handling, validation, and guarded database readiness for mission-critical DB Systems.
View DB System WorkloadsApplication Plans
Sequenced multi-tier recovery or cutover plans with approval gates, health checks, and evidence that shows what was verified and what remains customer-owned.
View Application PlansCold Standby Economics
Powered off, yet provably recoverable
Conventional standby
Recovery-target compute often runs continuously so it is ready for failover. That can mean paying for idle CPU and memory even when no recovery event occurs.
Yorigu cold standby
Yorigu keeps Disaster Recovery targets powered off until scheduled validation or actual failover. Steady-state cost is driven primarily by storage, while compute is used when readiness needs to be proven or recovery is invoked.
Illustrative: in steady state, cost is dominated by storage; compute is consumed during scheduled validation windows and actual failover. Validation and AutoHealing are what make the powered-off model operationally credible.
Next Step
Discuss Your Deployment
Yorigu can help assess the right deployment model based on your operational requirements and recovery objectives.