Applies to: Windows Server 2025 / 2022 / 2019 / 2016 / 2012 R2 / 2012 / 2008 R2 / 2008
Windows Server Backup can create full server, volume, system state, and bare-metal recovery backups. If the server cannot boot or a system disk fails, you can start Windows Recovery Environment (WinRE) and restore the server from a previously created backup.
The original version of this article was written for Windows Server 2008. The same core backup and bare-metal recovery model is still available in current Windows Server releases.
In This Article
- 1. Full Server vs. Bare-Metal Recovery
- 2. Install Windows Server Backup
- 3. Create a Bare-Metal or Full Server Backup
- 4. Create a Backup with WBAdmin
- 5. Perform a Bare-Metal Recovery
- 6. Key Takeaways
1. Full Server vs. Bare-Metal Recovery
A bare-metal recovery (BMR) backup contains the critical volumes required to recover the operating system and start the server again.
A full server backup includes all selected server volumes, not only the critical system volumes. This distinction matters when application data, Hyper-V virtual machines, databases, or other important files are stored on non-system volumes.
If you need both operating system recovery and all server data, use a full server backup or make sure all required non-critical volumes are protected separately.
2. Install Windows Server Backup
Windows Server Backup is not installed by default on current Windows Server releases. Install the feature from Server Manager or with PowerShell:
Install-WindowsFeature Windows-Server-Backup3. Create a Bare-Metal or Full Server Backup
- Open Windows Server Backup.
- Select Local Backup.
- Select Backup Once or configure a scheduled backup.
- For a complete server backup, select Full server.
- For a custom backup, select Bare metal recovery and any additional volumes that must also be protected.
- Select a local disk or remote shared folder as the backup destination.
- Start the backup and verify that it completes successfully.
Do not store the only copy of the backup on the same physical storage that you are protecting.
4. Create a Backup with WBAdmin
For a bare-metal capable backup of the critical volumes:
wbadmin start backup -allCritical -backupTarget:E:For a full backup that also includes an additional data volume:
wbadmin start backup -backupTarget:E: -include:C:,D: -allCriticalRun WBAdmin from an elevated command prompt. Adjust the backup target and included volumes for your environment.
5. Perform a Bare-Metal Recovery
- Boot the server from Windows Server installation media or another supported recovery environment.
- Select Repair your computer to enter Windows Recovery Environment.
- Make the backup location available. This can be a local disk or supported network location.
- Select the required backup version.
- Start the system image or bare-metal recovery.
- After recovery completes, restart the server and validate the operating system, applications, and data.
From Windows Recovery Environment, WBAdmin can also start a system recovery:
wbadmin start sysrecovery -version:<VersionIdentifier> -backupTarget:<BackupLocation>If the target server uses different disks or hardware, confirm the disk layout, storage drivers, BitLocker requirements, and application-specific recovery requirements before starting the restore.
6. Key Takeaways
- Windows Server Backup still supports bare-metal and full server recovery.
- BMR protects the critical volumes required to recover the operating system.
- Full server backup is the safer choice when important data exists on additional volumes.
- Test recovery procedures before an actual outage.
- Keep at least one backup copy on storage that is independent from the server being protected.
References
Cloud and infrastructure professional with nearly two decades of experience in enterprise IT environments, spanning public cloud, private cloud, and hybrid architectures.