Kyle Dunkerley
PIR-05 · Migration · April to May 2025

When the cutover changed.

I led planning, cutovers and health checks for a three-week Hyper-V to VMware move.

Scope

21 VMs

Five Hyper-V hosts to four VMware hosts, production and DR.

SQL server

3.5 TB

Total server storage across five drives.

The interruption

~6 hours on paper

The conversion locked the database at about 20%. Production stopped.

Option 1 · Stop

An uncertain release

Lose scan progress with no guarantee the database lock releases.

Option 2 · DR

Reconcile later

New orders would need merging. The DBA identified a risk of missed orders.

Option 3 · Chosen together

Complete the migration.

With the site manager and DBA: adjust, continue, finish. About four hours saved.

  • Next: rebuilt two smaller database servers rather than converting them.