How to Set Up System State Backup and Bare Metal Recovery on Windows Server 2019

Introduction to System State Backup and Bare Metal Recovery

System State Backup and Bare Metal Recovery (BMR) are two of the most critical recovery capabilities for Windows Server 2019. A system state backup captures the minimal set of OS components required to recover a server’s role configuration: the Windows Registry, COM+ Class Registration Database, boot files and Boot Configuration Data (BCD) store, and on domain controllers, Active Directory database and SYSVOL. Bare Metal Recovery goes further — it captures the entire server (all volumes required to boot and run the OS) in a format that can restore the server to completely new hardware without requiring a prior OS installation. Together, these two capabilities ensure that even a catastrophic hardware failure can be recovered quickly and completely. This guide covers creating and restoring system state and BMR backups using Windows Server Backup and PowerShell.

Understanding the Difference Between System State and BMR

A System State backup typically ranges from 5 GB to 20 GB depending on the installed roles (Active Directory adds approximately 1–5 GB to the backup). It does not include user data, application data, or the full Windows OS installation files — only the components necessary to restore the server’s configuration. System State backup is the appropriate recovery method when the OS is functional but the AD database, registry, or system configuration is corrupt.

A Bare Metal Recovery backup includes all critical OS volumes (System Reserved partition, C: drive, and any volumes hosting OS components), plus a system state. The BMR set is typically 30–80 GB. It is the appropriate recovery method when hardware has failed and you need to restore to replacement hardware, or when the OS itself is unbootable and Windows Recovery Environment (WinRE) will be used to restore from the backup.

Installing Windows Server Backup

Windows Server Backup must be installed before creating BMR or system state backups:

Install-WindowsFeature -Name Windows-Server-Backup -IncludeManagementTools

Verify installation:

Get-WindowsFeature -Name Windows-Server-Backup

Creating a System State Backup

Perform a system state backup to a local volume. The backup target must not be a critical volume (not C: on most systems). Ensure the target volume has sufficient free space — 30 GB minimum to account for the backup plus staging:

wbadmin start systemstatebackup -backupTarget:E: -quiet

To back up system state to a network share:

wbadmin start systemstatebackup -backupTarget:\backupserversharessystemstate -user:DOMAINbackupuser -password:BackupPass123 -quiet

Monitor backup progress — the backup runs in the foreground by default and outputs progress to the console. The -quiet flag suppresses the confirmation prompt but does not suppress progress output. A successful backup ends with the message “The backup operation successfully completed.”

Creating a Bare Metal Recovery Backup

Create a BMR backup by using the -allCritical flag in addition to the backup options. This instructs Windows Server Backup to include all volumes necessary for a bare metal recovery:

wbadmin start backup -backupTarget:E: -allCritical -systemState -vssfull -quiet

The -systemState flag ensures the system state is explicitly included (it is automatically included with -allCritical on most configurations, but explicit inclusion avoids ambiguity). The -vssfull flag performs a full VSS backup, truncating VSS backup history and ensuring the next backup captures all changed blocks.

To back up to a network share with BMR coverage:

wbadmin start backup -backupTarget:\backupserverbmr -user:DOMAINbackupuser -password:BackupPass123 -allCritical -systemState -vssfull -quiet

Scheduling Automated System State and BMR Backups

Create a scheduled task to automate nightly BMR backups. First, identify the backup disk’s identifier:

wbadmin get disks

Then create a scheduled backup policy targeting the dedicated backup disk:

wbadmin enable backup -addtarget:{DISK-GUID-HERE} -schedule:22:00 -allCritical -systemState -vssfull -quiet

Alternatively, use Task Scheduler for more flexibility (network share targets, custom scripts with error handling):

$action = New-ScheduledTaskAction -Execute "wbadmin.exe" -Argument "start backup -backupTarget:\backupserverbmr -user:DOMAINbackupuser -password:BackupPass123 -allCritical -systemState -vssfull -quiet"
$trigger = New-ScheduledTaskTrigger -Daily -At "22:00"
$settings = New-ScheduledTaskSettingsSet -ExecutionTimeLimit (New-TimeSpan -Hours 8) -Priority 7
Register-ScheduledTask -TaskName "Nightly-BMR-Backup" -Action $action -Trigger $trigger -Settings $settings -RunLevel Highest -User "NT AUTHORITYSYSTEM"

Restoring System State on a Running Server

System state restore on a non-domain controller does not require booting into recovery mode — it can be performed from a running Windows session. List available backup versions on the target:

wbadmin get versions -backupTarget:E:

Restore the system state from the most recent backup version (replace the version identifier with output from the above command):

wbadmin start systemstaterecovery -version:05/17/2026-22:00 -backupTarget:E: -quiet

The server restarts automatically after a system state restore. On domain controllers, a system state restore restores Active Directory. For an authoritative restore (to recover deleted AD objects), boot to DSRM mode first, then use ntdsutil to mark the restored objects as authoritative before the server replicates changes from other DCs.

Performing Bare Metal Recovery from Windows Recovery Environment

To restore a BMR backup to new or reimaged hardware, boot the server from Windows Server 2019 installation media. At the Install Now screen, click Repair your computer. Select Troubleshoot > System Image Recovery. Windows scans connected storage for available backup sets. Select the appropriate backup set (the most recent, or browse to the network share where the backup is stored).

In the Re-image your computer wizard, click Advanced and check Search for a system image on the network if the backup is on a network share. Enter the UNC path and credentials. Select the backup version and click Next. Review the restore configuration — the target disk will be completely overwritten with the contents from the backup. Click Finish to begin the restore. BMR restore typically completes in 30–90 minutes depending on the backup size and storage speed. The server reboots into the restored OS automatically after completion.

Verifying Backup Integrity

Periodically verify backup integrity to ensure backups are recoverable. Windows Server Backup does not have a built-in verify command, but you can validate a backup by performing a test restore to an alternate location. Alternatively, check the backup event log for errors after each backup job completes:

Get-WinEvent -LogName "Microsoft-Windows-Backup" | Where-Object { $_.Id -eq 4 -or $_.Id -eq 5 } | Select-Object TimeCreated, Id, Message | Sort-Object TimeCreated -Descending | Select-Object -First 10 | Format-List

Event ID 4 indicates success, Event ID 5 indicates failure. Any failures should be investigated and resolved immediately. For domain controllers, run repadmin /replsummary periodically to verify AD replication is healthy — a good system state backup combined with healthy AD replication significantly reduces recovery time objectives for AD failures.