I performed a test restore of a physical Windows Server 2022 domain controller that is backed up with the Veeam Windows Agent using a Full Computer (Bare Metal) backup. I restored it as a Hyper-V VM in an isolated network.
On the first boot, the restored VM repeatedly BSOD'd with CRITICAL_SERVICE_FAILED. After running CHKDSK from WinRE and letting Windows complete its repairs, the VM now boots normally. AD DS, DNS, and Netlogon all start successfully, and the restored DC appears healthy.
While troubleshooting, I checked the production server and found:
chkdsk C: /scan reports NTFS corruption in C:\Windows.old\… and recommends chkdsk /spotfix.
fsutil dirty query C: reports the C: volume is dirty.
0 KB bad sectors.
Active Directory is otherwise healthy in production.
The restored VM now reports a clean filesystem after CHKDSK.
Would you consider this a Windows/NTFS issue on the source server rather than a Veeam restore issue? Would you be comfortable scheduling chkdsk /spotfix on a production DC with verified backups and additional healthy domain controllers available? Any similar experiences?
submitted by /u/Undiscoveredspecie to r/sysadmin
[link] [comments]
Source: r/sysadmin · by /u/Undiscoveredspecie