Migrating Windows Server 2019 to Dissimilar Hardware. The easy pathway.

Moving a server operating system to entirely new hardware can be daunting, especially when the hardware is significantly different from the original. This post details our experience migrating a Windows Server 2019 installation from an HP EliteDesk G2 to a Dell OptiPlex 7090 using Veeam Backup & Replication, focusing on ensuring system stability post-migration.

The Challenge: Dissimilar Hardware

The primary challenge was the transition between two different hardware platforms (HP to Dell). This often introduces driver incompatibilities and potential instability if not handled correctly. Our goal was to perform a bare-metal restore that accounted for these hardware differences.

The Migration Process with Veeam

Here’s a breakdown of the steps we followed:

1. Full Backup: We started by taking a full backup of the existing HP EliteDesk G2 server using Veeam.
2. Boot with Recovery Media: We booted the new Dell OptiPlex 7090 using the Veeam Recovery Media (USB).
3. Load Drivers: Crucially, within the Veeam recovery environment, we loaded the necessary drivers for the Dell OptiPlex 7090. This allowed the recovery environment to recognize the target hard drive.
4. Restore: Once the target drive was accessible, we initiated the restore process from the backup.
5. Initial Boot: After the restore completed, we booted the Dell OptiPlex 7090 into Windows Server 2019.

Post-Migration Hiccups and Fixes

Even with careful planning, migrations can have bumps:

• System Freeze: We experienced a system freeze shortly after the first successful boot. A simple restart resolved this initial instability.
• VM Verification: After restarting, we booted up the server again and confirmed that our Hyper-V virtual machines were running as expected.
• Hyper-V Networking (pfSense Example): A specific challenge arose with a pfSense firewall running as a Hyper-V VM. Due to the dissimilar hardware, the network interface card (NIC) assignments needed adjustment within Hyper-V settings. Interestingly, the pfSense VM required a reboot after these settings were applied for the network configuration changes to take full effect.

Conclusion

Migrating Windows Server 2019 to dissimilar hardware was successful using Veeam. Key takeaways include the critical importance of injecting the correct drivers for the new hardware during the restore process and being prepared for minor troubleshooting steps post-migration, such as system restarts or VM-specific adjustments (like the pfSense NIC issue). Overall, Veeam proved to be a reliable tool for this complex task.