We reviewed PPK's three-node VMware estate and compared six options before selecting Azure Local, then planned and delivered the move.
The renewal changed the case for staying on VMware
Broadcom's VMware renewal model changed the economics of PPK's existing platform. The business needed to decide whether to keep VMware or change platform while accounting for its hardware lifecycle and the dependencies behind its virtual server workloads.
The replacement still had to provide local control and predictable access to business systems. We included migration, backup, recovery and ongoing support in the scope, so PPK could judge each option against the work required to move and operate the environment.
nodes in the original VMware estate
paths assessed before platform selection
virtual server workloads migrated
We compared six paths before selecting Azure Local. Each was considered against the existing hosts and workloads, performance needs, dependencies and migration risk.
Continue operating on the existing virtualisation platform
AssessedRetain VMware with a smaller estate
AssessedMove the VMware environment into Azure as an interim step
AssessedMove workloads to public cloud services
AssessedReplace VMware with a Nutanix platform
AssessedSelected as the local replacement platform
Azure Local kept the workloads PPK needed on site, on a Microsoft platform with a path to hybrid management, and let migration, backup and support run as one project.
We reviewed the three VMware nodes, host lifecycle and virtual machine footprint. Each workload was assessed for its dependencies, performance requirements and migration risk. That work established what had to move and informed the migration sequence.
We planned the order of migration, cutover windows and rollback arrangements before changing production systems. More than 20 virtual server workloads then moved to Azure Local through that planned sequence, with the dependencies identified during assessment carried into delivery.
We realigned backup to Azure Local and included recovery validation in the transition. This kept recovery within the migration scope, with protection addressed alongside the production workloads being moved.
We brought the Azure Local environment into ongoing managed infrastructure support after cutover. Our work continued beyond the migration, with the replacement platform, backup and recovery included in the supported environment.
A completed VMware exit with a supported local platform
PPK's virtual servers now run on Azure Local. The project changed both their underlying platform and the arrangements for operating and recovering them.
The migrated workloads no longer depend on renewing the VMware platform. Azure Local is now their local operating environment.
Protection was rebuilt for Azure Local during the move, and recovery was checked as part of the transition instead of being left until afterwards.
We carried the environment from cutover into our managed infrastructure support, covering the platform, backup and recovery together.
We review the renewal alongside your workloads, hardware and recovery requirements, then design and deliver the selected platform. Talk to us about the next decision for your infrastructure.
Prefer email? contact@inlightit.com.au