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

Yorigu Migrate

Yorigu Migrate for Proxmox

Machine and DB System Migration for Proxmox

Move physical, virtual, and database workloads to Proxmox VE with agentless preparation, staged cutover, validation, and rollback planning.

Discuss Deployment Read How It Works

Workload Coverage

Physical Servers

Physical Servers are replicated or migrated to the selected target without changing the source configuration.

Virtual Machines

Virtual Machines follow the same workflow as Physical Servers, with validation tracked through every phase.

DB Systems

DB Systems add Database-Aware consistency, validation, and cutover readiness for mission-critical database workloads.

Target-Specific Delivery

Controlled Migration to Proxmox VE

The Proxmox variant focuses on Proxmox VE target access, host or cluster placement, storage mapping, network mapping, cutover readiness, and operational handover planning.

  • Proxmox VE host or cluster placement
  • Storage and network mapping for private-cloud targets
  • Validation, cutover, and rollback evidence

Operational Controls

Product-Specific Controls

Validated Dry Runs

Dry runs use the same workflow model as the real cutover, producing validation results before production movement.

Planned Cutover

Cutover is handled as a controlled workflow phase with readiness and sequencing tracked before execution.

Defined Rollback Window

Rollback planning remains visible after cutover so post-migration decisions are not improvised.

Migration Validation

Validation confirms the migrated workload against the selected target before the migration is considered complete.

Database-Aware Workflows

DB System Coverage

Yorigu can automate migration workflows for physical servers, virtual machines, and mission-critical database systems. When database-aware coverage is required, DB Systems brings consistency, validation, cutover readiness, and recovery state into the same operational view as machine-level workflows for VMware, legacy, or on-prem movement toward Proxmox.

Database-aware workflows track consistency and validation state, so DB systems return in a usable, consistent state rather than as generic block-level copies. This matters most for transactional systems such as Oracle and SAP HANA.

View DB System Workloads

Database Engines

Oracle Microsoft SQL Server PostgreSQL MySQL SAP HANA

Machine-Only Packaging

Physical server and virtual machine coverage for environments that do not need database-aware workflows.

Machine + DB System Packaging

Machine + DB System packaging includes Physical Server and Virtual Machine coverage alongside Database-Aware workflows.

Machine-only migration is available for environments without mission-critical database system requirements.

For organization-specific licensing, deployment scope, or a POC License, contact Yorigu.

Next Step

Discuss Your Environment

Yorigu can help assess the right deployment model based on your operational requirements and recovery objectives.

Request a POC Read How It Works