Skip to content
Solutions

VMware Exit · Proxmox and Vates POC

Proxmox or Vates POC: validate before production.

Validate one target or compare both using representative workloads. Test architecture, migration, resilience and operations against criteria agreed before testing.

Two targets, one validation framework

Validate an existing preference or choose between Proxmox VE and Vates. Business objectives are shared; architectures and procedures are assessed separately.

Proxmox VE

Validate the Proxmox VE cluster, selected storage, VMware imports and operational procedures. Test PBS when selected, or qualify your existing backup solution if retained.

On your infrastructure or VSHIFT Cloud. HA and performance validation require representative topology and resources; nested labs support discovery.

Scope my Proxmox POC →Explore VSHIFT Cloud environments →

Vates · XCP-ng / Xen Orchestra

Validate the XCP-ng pool, Xen Orchestra, selected storage and VMware imports. Include restores, availability and administration tasks in the test protocol.

On infrastructure suited to the project. Vates is planned for VSHIFT Cloud; self-service provisioning is not yet available in the portal.

Scope my Vates POC →Explore the Vates migration path →

Demo, technical pilot or POC?

The required level of evidence determines the right format. A product demo is not enough for a production decision.

Demonstration
Review the interface and core features without drawing conclusions about estate compatibility.
Technical pilot
Test a limited scope and one specific hypothesis with targeted measurements.
Production POC
Validate architecture, workloads, resilience, backup, DR and operations against written GO / NO-GO criteria.

What we test for each target

Agree acceptance thresholds before testing: permitted downtime, application latency, RTO/RPO and operational effort. Comparative tests use the same datasets and scenarios; hardware and resource differences are recorded.

Agree acceptance thresholds before testing: permitted downtime, application latency, RTO/RPO and operational effort. Comparative tests use the same datasets and scenarios; hardware and resource differences are recorded.
AreaProxmox VEVatesExpected evidence
Migration and applicationsImport into VE, guest drivers, networking and application startup.Import into XCP-ng, guest tools, networking and application startup.Downtime, data consistency, business acceptance and return to VMware.
Storage and performanceShared storage, Ceph or ZFS as selected in the design.Shared SR or XOSTOR as selected in the design.Latency, throughput, usable capacity and degraded behaviour under target load.
High availabilityQuorum, fencing and protected VM restarts.Pool HA, storage heartbeat and protected VM restarts.Host loss timeline, application recovery and remaining capacity.
Placement and maintenanceSelected HA/CRS rules, live migration and behaviour under load.Selected placement and XO balancing rules, migration and maintenance.Observed moves, limits, exceptions and host evacuation time; gaps against actual DRS usage.
Backup and DRPBS if selected, or compatibility of the retained third-party backup.Selected XO backup and replication, or qualified third-party integration.VM and application restore, measured RTO/RPO and management recovery.
Operations and budgetAccess, monitoring, updates and selected VE/PBS support.XO access, monitoring, updates and selected Vates support.Executed runbooks, responsibilities, transition costs and recurring budget per target.

Adapt the protocol to selected versions, options and licences. Functional equivalence is not assumed. Failure tests use an isolated, authorised environment; results depend on measurements.

Four decision gates

Each gate links an input, a test, an expected item of evidence and a decision. The POC advances only when the required evidence is available.

01

Scope and target architecture

Input
VMware inventory, dependencies, network, storage and backup constraints.
Test
Cluster, segmentation and storage design, with representative workload selection.
Evidence produced
Documented architecture, acceptance criteria and risk matrix.
Possible decision
Testable scope or scoping work to revisit.
02

Performance and compatibility

Input
Representative workloads and agreed performance objectives.
Test
Migration, storage and network benchmarks, and application validation.
Evidence produced
Comparable measurements, documented gaps and sizing adjustments.
Possible decision
Workloads accepted, adapted or excluded.
03

Resilience and recovery

Input
Criticality, RTO/RPO, HA policies and selected failure scenarios.
Test
Node loss, storage degradation, restore and rollback.
Evidence produced
Test timeline, HA/DR results and recovery procedures.
Possible decision
Continuity level accepted or remediation required.
04

Operations and GO / NO-GO

Input
Monitoring, backup, runbooks and consolidated validation criteria.
Test
Representative operations and a joint review of the collected evidence.
Evidence produced
Validation report, reservations, migration plan and rollback scenario.
Possible decision
GO, conditional GO or documented NO-GO.

What you get

Each deliverable is documented, verifiable and reusable by your teams to operate the infrastructure autonomously.

  • Phase validation report
  • Documented architecture
  • Storage benchmark results
  • HA & DRP test report
  • Recovery procedures
  • Operational runbooks
  • Objective go/no-go decision
  • Team training included

Prepare a POC

Scope the target, workloads, environment and GO / NO-GO criteria. If the choice is open, use a protocol that compares both platforms.