Introduction
Migrating enterprise workloads between virtualization platforms is no longer rare—it's a necessity for organizations chasing flexibility, cost savings, and modernization. This post distills the newly released implementation guide, Cross-Platform Virtual Machine Migration, into a concise, step-by-step journey. The scenario simulates an “existing” VMware vSphere cluster running on an older Hitachi VSP F700 storage system, migrating into a modern Microsoft Hyper-V failover cluster powered by the latest Hitachi VSP One Block 28. Orchestration is handled by System Center Virtual Machine Manager (SCVMM), demonstrating how legacy environments can be transitioned to next-generation infrastructure with minimal, planned disruption.
Why SQL Server?
It’s everywhere—mission-critical, stateful, and demanding. Migrating a clustered SQL Server (on Windows Server Failover Cluster with Raw Device Mapping disks) is one of the toughest, most representative challenges. If you can move SQL Server, you can move almost anything. Success here proves your migration process is robust and ready for real-world enterprise workloads.
Migration Architecture & Prerequisites
Figure - Schematic diagram
Source Environment
Why this setup?
VMware vSphere clusters with RDM disks are a classic choice for high-availability SQL Server deployments. It’s a scenario many IT teams will recognize.
- Virtualization: VMware vSphere 8.0 U3, two bare-metal ESXi hosts
- Storage: Hitachi VSP F700 SAN (RDM disks for SQL data/quorum)
- Cluster: Virtual Windows Server Failover Cluster (WSFC) hosting SQL Server 2022
- Networking: 10 GbE for VM traffic, 1 GbE for management
Target Environment
Why this target?
Hyper-V on Windows Server 2025 brings advanced virtualization and seamless integration with Microsoft tools. Hitachi VSP One Block 28 delivers reliable, scalable storage—perfect for demanding workloads. Migrating here means easier growth and streamlined operations.
- Virtualization: Microsoft Hyper-V on Windows Server 2025, physical WSFC cluster
- Storage: Hitachi VSP One Block 28 SAN (Cluster Shared Volumes)
- Networking: 10 GbE for migration/heartbeat, 1 GbE for management
Key Prerequisites
- Consistent domain membership (same domain controller for both environments)
- Pre-provisioned storage and network
- SCVMM 2025 installed, both clusters added to VMM fabric
- Careful planning for downtime, feature compatibility, and manual steps
Migration Phases
Migrating clustered VMs (the virtual WSFC) from VMware to Hyper-V is a two-phase process—each phase tackles a different technical challenge.
Why two phases?
OS volumes and data volumes have unique requirements. SCVMM handles VM conversion, but clustered SQL Server data (on RDM disks) needs specialized storage migration to keep everything intact. Splitting the process minimizes downtime and risk.
Figure - Existing data in Microsoft SQL Server 2022 database - to be verified post-migration
Phase 1: OS Volume Migration with SCVMM
- SCVMM inventories source VMs
- Admins select target Hyper-V hosts
- Offline conversion: VMs are powered off for consistency
- Validation: Migrated VMs appear in Hyper-V Failover Cluster Manager, ready for setup
Note: No live migration—VMs must be powered off. Only one VM migrates at a time.
Phase 2: Data Volume Migration with Hitachi UVM
- Hitachi Universal Volume Manager (UVM) migrates LUNs from old to new storage
- ShadowImage/Thin Image (SI/TI) creates local replicas for safety
- LUNs mapped to the new cluster, preserving compatibility
Step-by-Step Migration Workflow
A successful migration is all about orchestration. For detailed instructions, please check the implementation guide. Here’s how it works at high level:
Pre-Migration
- Gracefully stop SQL cluster role
- Detach RDM disks, record LUN IDs/WWNs
- Power off VMs
Migration Execution
Figure – Add VMware vSphere Cluster to the VMM fabric
- Use SCVMM for VM conversion/migration
- Use UVM for storage migration and replication
- Map LUNs to new cluster
Figure – Configure WWPN on Fibre Channel Adapter
Post-Migration
- Remove old network adapters, add new ones
- Rescan disks, bring LUNs online, assign drive letters
- Recreate cluster resources and configure quorum
Validation & Cutover
- Bring SQL Server role online, test failover
- Confirm data integrity
- Disconnect legacy storage, clean up SAN zoning
- Ensure new environment is fully independent
Why will this workflow succeed?
Every step is designed to prevent data loss and ensure compatibility. Proven enterprise tools (SCVMM, Hitachi UVM) handle the heavy lifting, while careful validation and severance guarantee a clean, reliable cutover.
Lessons Learned & Best Practices
- Schedule migration for off-peak hours: Cross-hypervisor migrations almost always cause service interruptions—plan for minimal user impact.
- Document everything: LUN IDs, WWNs, network settings—leave nothing undocumented. The more details you capture, the smoother your troubleshooting and rollback.
- Automate repetitive tasks: Use orchestration tools and scripts wherever possible to reduce manual errors and speed up the process.
- Test thoroughly before severing legacy connections: Know your test cases and validate every critical function. Don’t disconnect the old environment until you’re certain the new one works.
- Be ready for manual tweaks: Even with automation, expect to make hands-on adjustments—especially with complex network or storage configurations.
Conclusion
Migrating clustered SQL Server workloads from VMware to Hyper-V is demanding—but absolutely doable. With careful planning and validation, you can ensure data integrity and minimal downtime.
Key Takeaways:
- Migrating SQL Server in a virtualized Windows Server Failover Cluster (WSFC) on vSphere with Raw Device Mapping (RDM) disks to another hypervisor demonstrates the technical depth and reliability of this migration framework.
- Detailed documentation, clear communication, and a willingness to address manual steps are essential for a smooth migration.
- The result is a Hyper-V environment with Hitachi storage that’s ready for production workloads, offering improved manageability and operational confidence.
This methodology isn’t just a checklist—it’s a flexible framework. The principles, thought process, and steps outlined here can be adapted to migrations between many different platforms, storage systems, and workloads. Whether you’re moving from VMware to Hyper-V, or tackling other source and target combinations, thoughtful planning and proven tools will help you navigate the complexities and achieve a smooth transition.
#HitachiIntegratedSystems #migration