INFRASTRUCTURE CASE STUDY

ESXi to Proxmox Migration and PBS Recovery

Migration and recovery planning for a legacy VMware ESXi lab environment moving into Proxmox VE with Proxmox Backup Server. The work focused on understanding ESXi compatibility limits, moving virtual machines into a Proxmox-managed state, validating backups in PBS, and documenting a repeatable recovery path.

Status: Completed Type: Infrastructure Migration Role: Operator / Engineer Focus: Migration and Recovery Context: Professional Experience - Sanitized

EVIDENCE AT A GLANCE ESXi to Proxmox VE PBS integration Backup integrity validation Documented recovery path

PROBLEM

The lab needed to move from ESXi into a Proxmox-backed recovery model.

The lab environment included virtual machines running under VMware ESXi, while the target recovery platform was Proxmox Backup Server. PBS integrates cleanly with Proxmox VE, but it does not directly back up standalone ESXi workloads in the same native way. That created a migration and compatibility problem: the virtual machines first had to be inventoried, exported or imported, validated under Proxmox VE, and only then protected through PBS.

COMPATIBILITY CONSTRAINT

PBS protected the Proxmox side of the environment, not ESXi directly.

ESXi source environment

Existing workloads were running under VMware ESXi, which required VM inventory, snapshot review, power-state checks, export/import planning, and validation before the systems could be treated as Proxmox-managed workloads.

PBS target environment

Proxmox Backup Server was used as the recovery platform after workloads were brought under Proxmox VE management. This made backup validation, datastore organization, and restore planning part of the migration workflow rather than a separate afterthought.

ARCHITECTURE

ESXi was the source, Proxmox VE became the platform, and PBS became the recovery layer.

flowchart TD
  ESXI[VMware ESXi Source Host] --> INV[VM Inventory and Compatibility Review]
  INV --> SNAP[Snapshot and Power-State Cleanup]
  SNAP --> EXPORT[Export or Import VM Workload]
  EXPORT --> PVE[Proxmox VE Target Host]
  PVE --> VALIDATE[Boot, Driver, Network, and Storage Validation]
  VALIDATE --> PBS[Proxmox Backup Server]
  PBS --> VERIFY[Backup Verification]
  VERIFY --> RECOVER[Restore and Recovery Readiness]

ENGINEERING WORK

Migration was treated as a validation workflow, not just a file move.

ESXi inventory

Identified source workloads, VM names, power states, storage placement, networking requirements, and migration readiness before moving systems into the Proxmox environment.

Snapshot cleanup

Reviewed and removed legacy snapshot conditions that could interfere with clean export, import, backup, or validation workflows.

Proxmox validation

Validated imported workloads under Proxmox VE, including boot behavior, virtual hardware compatibility, storage attachment, and network reachability.

PBS protection

Added migrated workloads to the Proxmox Backup Server workflow and confirmed backup completion, datastore visibility, and verification status.

VALIDATION

Migration was not complete until the workload could be backed up and verified.

Import validation

Confirm VM appears under Proxmox VE.
Confirm expected virtual disks are attached.
Confirm VM can boot or reach a known-good stopped state.
Confirm network configuration is understood before production use.

Backup validation

Run backup into the PBS datastore.
Confirm backup artifact appears under the expected VM ID.
Run or confirm verification status.
Document restore path and operational notes.

RECOVERY MODEL

The recovery path became Proxmox-native after migration.

Instead of treating PBS as a direct ESXi backup tool, the workflow moved systems into Proxmox VE first. Once the workloads were Proxmox-managed, PBS could be used for backup scheduling, datastore organization, verification, and restore readiness.

Before migration

ESXi workloads required separate handling, compatibility review, and migration planning before they could participate in the Proxmox backup workflow.

After migration

Proxmox-managed workloads could be backed up into PBS, verified, and included in a repeatable recovery process.

OUTCOME

The migration clarified the boundary between ESXi, Proxmox VE, and PBS.

The migration work clarified the boundary between ESXi, Proxmox VE, and Proxmox Backup Server. Instead of treating PBS as a direct ESXi backup tool, the workflow moved systems into Proxmox management first, then protected them through PBS. This created a cleaner operating model for future lab recovery, backup validation, and VM lifecycle management.