A file system restore using Symantec Netbackup or Backup Exec to perform a DR of a Windows based system to another server with dissimilar hardware may result in a non-bootable Operating system.
The recovered system may fail to boot; get struck on a blue screen or display a Microsoft error code on reboot after a successful restore.
A hardware abstraction layer (HAL) is a layer of programming that allows the operating system to interact with a hardware device at a general or abstract level rather than at a detailed hardware level. The HAL abstracts low-level hardware details from the operating system and provides a common programming interface to devices of the same type (such as video adapters).
HAL, on Microsoft operating systems since Windows 2000, is implemented via the kernel-mode hal.dll module. HAL also prevents applications from directly accessing the system memory, CPU, or hardware devices - a method that can prevent many device conflicts and crashes. By default, the Hal.dll is not backed up as part of system state, however the Kernel32.dll is. Therefore, if we try to restore a backup onto a computer that requires a different HAL (for example, to support a multiprocessor environment) compatibility issues may arise between the new HAL and the original Kernel32.dll
A file system restore of System State data using Netbackup or Backup Exec is supported only when we are restoring to the original machine (same hardware). This is more of a limitation imposed by Microsoft’s HAL and is described in the article below….
Microsoft does not support restoring a system state backup from one computer to a second computer of a different make, model, or hardware configuration”
This applies to all Windows OS (32 and 64 bit) since Windows 2000