Use Case
Physical to OCI Disaster Recovery
For physical workloads that need an OCI recovery target but still require careful treatment of OS state, hardware dependencies, network mapping, and application role.
Operating Context
Where this use case fits
This use case fits when the source estate, target model, operating system coverage, RTO/RPO expectations, validation evidence, database scope, and recovery or migration governance must be planned together.
Source environment considerations
Physical servers are assessed by operating system state, disk layout, hardware dependencies, network dependencies, application role, and recovery or migration objective.
OCI target operating model
OCI delivery brings tenancy access, network mapping, storage placement, validation evidence, and recovery or cutover readiness into a single planning model.
Agentless
Yorigu coordinates access, target preparation, validation evidence, and lifecycle state through the orchestration layer while keeping the source-side operating model lightweight.
Lifecycle
Recovery readiness, not just replication
The operating method is framed around recovery readiness: preparation, synchronization, validation, failover execution, and failback planning.
PrepareSyncValidateFailoverFailback
Related Yorigu Product
Yorigu Disaster Recovery for OCI provides the Yorigu product scope for this use case. Detailed coverage, packaging, and DB System options are outlined on the product page.
Review Product ScopeNext Step
Confirm fit for your environment
A Yorigu scope discussion confirms operating system coverage, access model, network reachability, target placement, DB System requirements, validation expectations, and handoff criteria before implementation.