A full system restore test that boots on the same hardware from which the backup was created proves that the backup file is intact. It doesn't show whether you can restore the server on different hardware than the current one, though.
This distinction is more important in 2026 than it used to be.
Semiconductor lead times reached 40 weeks in March 2026 (Accuris, 2026), and TrendForce has cut its 2026 server shipment growth forecast from 20% to 13% because of extended component lead times. (The Register, citing TrendForce, April 2026)
If a server fails today, the replacement you receive may not be the same model you usually order. With lead times for new units stretching for months, MSPs are increasingly filling the gap with refurbished hardware, a different vendor's model, or whatever is in stock. This means you might not get the specific unit you're used to. IT hardware brokers report rising demand for refurbished and alternative-vendor equipment because standard channel orders are being pushed to the back of the line.
This post explains what can go wrong when the hardware doesn't match and how to perform a restore test with dissimilar hardware without requiring a warehouse of spare servers.
Bare Metal Restore (BMR) and most image-based recovery tools do support restoring to dissimilar hardware. Microsoft specifically recommends BMR backups for Active Directory recovery because they can be restored to different hardware or even a different operating system (OS) instance. Third-party tools have built entire features around this capability, such as Acronis', Veeam's, and NovaBACKUP's dissimilar-hardware and P2V options.
For one of these restores to boot, the right drivers must be injected, the boot mode must match, and the target disk must be equal to or larger than the original. If any of these conditions are not met, you will end up with a valid-looking image and a server that won't start.
While matching drivers when restoring the operating system to a different server is less risky than it used to be for most standard configurations, there are still configurations and setups that don't cooperate as well.
Even with today's less error-prone systems, the following could break when the hardware changes:
None of these issues appear in a file-level restore test, and most of them won't appear in a same-hardware image restore either. These issues only surface when the target hardware is different. Due to hardware shortages and increased prices in 2026, this is a real scenario you're likely to face.
If the server in question is a domain controller, getting the OS to boot on new hardware is only half the battle. Restoring the Active Directory System State has its own strict prerequisites. For example, the machine name must match the original, the Windows build and Service Pack level must match exactly, and the target must already be elevated to a domain controller before you can restore AD onto it. Rebuilding on a machine with a different name won't result in a current, functioning AD by itself. You will likely need to perform a proper Directory Services Restore Mode (DSRM) process to update the System State, which is separate from the disaster recovery image restore process.
This is why treating a domain controller restore to different hardware as its own test case, separate from a standard file or application server restore, is important.
There is also a hard limit on how old a backup can be. Active Directory enforces a tombstone lifetime, which is the maximum age that a System State backup can be and still be restored cleanly, without causing lingering objects or replication failures. Most current ADs default to 180 days. Domains that predate Windows Server 2003 SP1 default to 60 days. If your only backup of a domain controller is older than this limit, Microsoft's own guidance recommends rebuilding the domain from a surviving DC rather than restoring the outdated backup.
You don't need a shelf full of spare servers to rehearse this. For example, NovaBACKUP lets you save a system image as a VHDx file that you can mount as a virtual machine in Hyper-V. This provides an inexpensive way to simulate a restore to dissimilar hardware. Restoring onto a VM with a different virtual hardware generation than the original host will surface most of the same driver, boot mode, and firmware issues that would be encountered when restoring to an unfamiliar physical server.
A few specific NovaBACKUP capabilities are directly relevant here. Image backups can be restored to the same or different hardware or mounted as a virtual machine. When creating the image, you can include specialized drivers, such as RAID controller drivers, for installation on the target machine. This addresses the most common cause of a restore that boots to a black screen. Additionally, because images can be exported as VHDx, physical-to-virtual restores are standard.
Ultimately, it comes down to regularly testing the system backup on different hardware so you know how it behaves and how long it takes. Here's a simple, step-by-step testing scenario:
The 2025 State of Ransomware report by Sophos found that the percentage of organizations requiring more than a month to recover from an attack decreased from 34% to 18% year over year. This improvement aligns with organizations that regularly perform recovery tests and document their findings.
Incorporate a dissimilar-hardware restore test into your regular schedule. For critical systems, perform this test at least annually and immediately after any major platform change, such as a hardware refresh or hypervisor migration. This documentation serves as evidence for cyber-insurance underwriters and auditors. It also provides clients who have never seen a backup dashboard with concrete proof that their recovery plan works.
Visit our Disaster Recovery page to see how NovaBACKUP handles disaster recovery restores to the same or different hardware. Read more on our blog, How to Test Your Disaster Recovery Plan: A Complete Guide to Backup Restorability.
FAQ
No, because a restore test that boots on the same hardware from which the backup was created only proves that the backup file is intact. It doesn't prove that the backup can be restored on different hardware since driver, boot mode, and disk layout issues only arise when the target machine changes.
FAQ
In March 2026, semiconductor lead times reached 40 weeks, and TrendForce cut its server shipment growth forecast for the year from 20% to 13% due to extended component lead times. When a server fails, it is increasingly replaced with a refurbished unit, a model from a different vendor, or whatever is in stock, rather than with an exact match. Therefore, a same-hardware restore test no longer reflects what will actually happen during a real recovery.
FAQ
Yes. BMR and most other image-based recovery tools support restoring to dissimilar hardware. Microsoft specifically recommends using BMR backups for Active Directory recovery because they can be used with different hardware or even a different OS instance. NovaBACKUP, Acronis, and Veeam all offer options for restoring to dissimilar hardware and for P2V (physical-to-virtual).
FAQ
Most failures occur in five areas:
FAQ
Getting the OS to boot is only half the job. To restore the Active Directory System State, the machine name must match the original, the Windows build and Service Pack level must match exactly, and the target must already be elevated to a domain controller before the AD restore. This usually necessitates a Directory Services Restore Mode (DSRM) process, which is separate from the disaster recovery image restore itself.
FAQ
Yes. Active Directory enforces a tombstone lifetime, which is the maximum age that a System State backup can be and still be restored cleanly, without creating lingering objects or replication failures. The default is 180 days for most current Active Directory environments and 60 days for domains predating Windows Server 2003 SP1. If the only available backup is older than this limit, Microsoft recommends rebuilding the domain from a surviving domain controller rather than restoring the outdated backup.
FAQ
Save a system image as a VHDx file and mount it as a virtual machine in Hyper-V, which is supported by NovaBACKUP. Restoring to a VM with different virtual hardware than the original host will surface most of the same driver, boot mode, and firmware issues that would be encountered when restoring to an unfamiliar physical server, but without the cost of maintaining spare hardware.
FAQ
At least annually for critical systems and immediately after any major platform change, such as a hardware refresh or hypervisor migration. According to Sophos's 2025 State of Ransomware report, the percentage of organizations needing more than a month to recover from an attack decreased from 34% to 18% year over year. This trend aligns with organizations that regularly test and document their recovery process.