How to Configure System State Backup and Bare Metal Recovery on Windows Server 2012 R2

How to Configure System State Backup and Bare Metal Recovery on Windows Server 2012 R2

A system state backup captures the critical OS configuration components required to restore a Windows Server 2012 R2 to a functional state without reinstalling the operating system. It includes the registry, the COM+ class registration database, Active Directory (on domain controllers), SYSVOL, IIS metabase, Certificate Services database, and the boot files. A Bare Metal Recovery (BMR) backup extends this further by capturing all critical volumes required to boot and run the server, enabling complete server restoration onto dissimilar hardware. This guide covers configuring both system state and BMR backups, and walks through the recovery procedures.

Prerequisites

Windows Server Backup feature must be installed. A backup destination with sufficient capacity is required — system state backups typically range from 2 GB to 15 GB depending on the server role (domain controllers with large NTDS databases can be significantly larger). BMR backups require space equivalent to all critical volumes. A Windows Server 2012 R2 installation media (ISO or DVD) is needed for BMR recovery as it boots the Windows Recovery Environment.

Step 1: Understand What is Included

System state backup includes: Registry, Boot files, COM+ class registration database, Active Directory Domain Services database (NTDS.dit on DCs), SYSVOL folder (on DCs), Cluster service information (on cluster nodes), Certificate Services database (on CA servers), and IIS metabase configuration.

BMR backup includes everything in a system state backup plus: The Windows OS volume (typically C:), All boot-critical volumes needed to start Windows, and enough information to restore to bare (empty) hardware.

Step 2: Configure System State Backup via WBADMIN

Perform an immediate system state backup to a network share:

wbadmin start systemstatebackup -backupTarget:\BackupServer01BackupsSystemState -quiet

Perform a system state backup to a local drive:

wbadmin start systemstatebackup -backupTarget:E: -quiet

List available system state backup versions:

wbadmin get versions -backupTarget:\BackupServer01BackupsSystemState

Step 3: Configure BMR Backup via WBADMIN

A bare metal backup includes all critical volumes. Perform an immediate BMR backup:

wbadmin start backup -backupTarget:\BackupServer01BackupsBMR -allCritical -systemState -quiet

The -allCritical flag ensures all volumes required for bare metal recovery are included automatically. The -systemState flag adds the system state backup on top of the BMR volumes.

Step 4: Schedule Automated Backups via PowerShell

Create a scheduled full BMR and system state backup using the Windows Server Backup PowerShell module:

Import-Module WindowsServerBackup

$policy = New-WBPolicy
$networkTarget = New-WBBackupTarget -NetworkPath "\BackupServer01BackupsBMR" -Credential (Get-Credential)
Add-WBBackupTarget -Policy $policy -Target $networkTarget
Add-WBBareMetalRecovery -Policy $policy
Add-WBSystemState -Policy $policy
Set-WBSchedule -Policy $policy -Schedule 22:00
Set-WBVssBackupOption -Policy $policy -VssBackupType WBVssFullBackup
Set-WBPolicy -Policy $policy
Get-WBPolicy

Step 5: Create a BMR Bootable Recovery Environment

Prepare the Windows Server 2012 R2 installation media for BMR recovery. When recovering onto bare hardware, boot from the Windows Server 2012 R2 installation DVD or USB, select the appropriate language settings, and then click Repair your computer instead of Install now.

In the recovery environment, navigate to Troubleshoot → System Image Recovery. Windows RE will search for available system image backups on locally attached drives. To recover from a network backup, click Select a system image and then Advanced → Search for a system image on the network, then enter the UNC path to the backup.

Step 6: Perform a System State Recovery

System state recovery can be performed without rebooting if the server is online (for most components). For domain controllers, Active Directory restore requires rebooting into Directory Services Restore Mode (DSRM).

Recover system state from a backup version:

# List available versions first
wbadmin get versions -backupTarget:\BackupServer01BackupsSystemState

# Recover system state (replace date/time with actual backup version)
wbadmin start systemstaterecovery -version:05/15/2026-22:00 -backupTarget:\BackupServer01BackupsSystemState -quiet

For Active Directory authoritative restore on a domain controller (restores deleted AD objects), boot into DSRM (press F8 at boot, select Directory Services Restore Mode) and run:

wbadmin start systemstaterecovery -version:05/15/2026-22:00 -authsysvol -quiet

Step 7: Perform Bare Metal Recovery

Boot from the Windows Server 2012 R2 installation media on the replacement or recovered server. After language selection, choose Repair your computer → Troubleshoot → System Image Recovery. The recovery wizard will guide you through selecting the backup image from either an attached drive or a network UNC path.

On the Select a system image backup page, choose Use the latest available system image or select a specific date/time. On the Choose additional restore options page, you can choose to format and repartition disks (recommended for bare-metal restoration to ensure the target disk matches the backup), or choose to exclude disks if the server has additional data disks that should be preserved.

For recovery to dissimilar hardware (different NIC or storage controller), Windows RE automatically injects drivers from the installed driver store. If the hardware is significantly different, you may need to provide driver media during the recovery process.

Step 8: Verify Recovery and Post-Recovery Steps

After BMR recovery completes and the server reboots, verify system functionality:

# Verify critical services are running
Get-Service -Name @("Netlogon","DNS","NTDS","W32Time","BITS") | Select-Object Name, Status

# Verify event log is clean of critical errors
Get-WinEvent -LogName System -MaxEvents 50 | Where-Object {$_.Level -le 2} | Select-Object TimeCreated, LevelDisplayName, Message | Format-List

# Check Active Directory health on domain controllers
dcdiag /test:advertising /test:fsmocheck /test:replications

For domain controllers, force AD replication after recovery to synchronise with other DCs:

repadmin /syncall /AdeP

Summary

System state and BMR backups on Windows Server 2012 R2 form the foundation of a complete server recovery capability. System state backups enable rapid recovery of OS configuration, Active Directory, and application settings without a full reinstall, while BMR backups provide the ultimate insurance policy for complete server failures. Regular scheduled BMR backups, combined with tested recovery procedures and documented RTO/RPO targets, ensure your organisation can recover from any server failure scenario within an acceptable timeframe.