Decision Paths

Recovery and migration paths for critical workloads

Compare workload routes for VMware, physical servers, DB Systems, and application-scoped recovery or cutover across OCI, Proxmox VE, and OLVM targets.

Decision Model

Start with workload, target, and operating risk

A useful recovery or migration plan starts with the workload type, the target platform, and the risk that must be controlled: failover readiness, cutover timing, database consistency, validation evidence, or rollback.

Scope the route

Source: VMware, Physical, or DB Systems Target: OCI, Proxmox VE, or OLVM Objective: Disaster Recovery or Migration Scope: machine, database, or application plan

Machine Workload Paths

VMware and physical-server recovery or migration

OCI Proxmox VE OLVM

Use this area when the workload is primarily a machine estate and the decision is the landing zone, recovery posture, cutover window, and rollback plan.

VMware estate exit or protection Physical-server modernization Validated recovery or cutover evidence
Physical-server use cases are listed with the machine workload paths.

DB-Aware Use Cases

Database-aware migration and disaster recovery

View DB System Workloads

Use this area when the database is not just a guest workload. Engine support, consistency state, validation evidence, failover readiness, and rollback assumptions need to be visible before the project is scoped.

Oracle Database Microsoft SQL Server PostgreSQL MySQL MongoDB SAP HANA

Application-Centric Use Cases

When the application is the unit of recovery or cutover

View Application Plans

Use Application Plans when the recovery or cutover decision spans multiple machines, database tiers, application tiers, approval gates, and post-event evidence.

Application dependency order Customer approval gates Business-service evidence