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

Database-Aware Workload Coverage

Database-Aware Disaster Recovery and Migration

Yorigu DB System Workloads extends Disaster Recovery and Migration beyond generic Machine movement. Database consistency, validation, cutover readiness, and recovery state stay visible for Oracle, Microsoft SQL Server, PostgreSQL, MySQL, and SAP HANA workloads.

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.

Why It Matters

Database Workloads Need More Than Machine Movement

Database workloads often require consistency handling, replication alignment, validation, cutover planning, and recovery readiness beyond the surrounding Machine workflow. Yorigu keeps these requirements inside the same operational lifecycle.

Database Consistency

Application-Consistent Recovery

For mission-critical Oracle, SQL Server, PostgreSQL, MySQL, and SAP HANA systems, the goal is a consistent, usable database on the target side, validated as part of the workflow.

Coverage

Where DB System Workloads Applies

  • Physical database servers
  • Virtual Machines running database workloads
  • Oracle, Microsoft SQL Server, PostgreSQL, MySQL, and SAP HANA environments
  • Disaster Recovery workflows that need validation and failback readiness
  • Migration workflows that need dry-run, cutover, and rollback planning

Yorigu Disaster Recovery

DB System Workloads in Disaster Recovery

Recovery State

Recovery state remains visible before a real failover event.

Replication Alignment

Replication and alignment status stay visible during normal operation.

Validation Evidence

Validation results are tracked as part of the recovery lifecycle.

Failover Readiness

Failover readiness reflects tracked workflow state and validation results.

Failback Preparation

Failback readiness remains visible before production ownership moves back.

Yorigu Migrate

DB System Workloads in Migration

Target Assessment

The source database environment is assessed against the selected target platform.

Wave Planning

Workload waves are planned before committing cutover.

Dry-Run Readiness

Dry-run state is reached before any production cutover.

Cutover Planning

Cutover planning keeps readiness, sequencing, and validation in one workflow.

Rollback Visibility

Rollback planning remains visible for post-cutover decisions.

Platform Scope

Source-Independent Database Coverage

DB System Workloads applies across supported Yorigu targets and source form factors. It can cover Physical database servers, VM-hosted database systems, and customer-managed database environments under Database-Aware packaging.

Packaging

Scoped by DB System

DB System Workloads can be included when database-aware workflow coverage is required. Capacity is scoped by DB System rather than by individual database, so environments with many small databases on the same server can be evaluated as one operational system.

This keeps packaging aligned with the operational DB System. A server hosting many small databases counts as one DB System for scoping.