Use Case
DB-Aware Proxmox Migration
For organizations that want a private target for database workloads while keeping DB System scope, validation, and handoff criteria visible.
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
VMware vSphere / ESXi environments often combine mixed operating systems, disk layouts, network dependencies, and business-critical applications that must be planned as one workload portfolio.
Proxmox VE target operating model
Proxmox VE delivery brings customer-managed host or cluster placement, storage mapping, network assumptions, validation evidence, and operational handoff into the same 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
Controlled migration, with validation and rollback planning
The operating method is framed around migration control: assessment, preparation, dry-run, cutover, validation, and rollback planning.
AssessPrepareDry RunCutoverValidateRollback Planning
Related Yorigu Product
Yorigu Migrate for Proxmox 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.