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

Protecting a Windows Server 2016 installation requires more than simply backing up user data. The operating system itself, including the registry, the Active Directory database, boot files, and the COM+ class registration database, must be captured in what is known as a System State backup. For the most comprehensive protection, a Bare Metal Recovery backup captures the entire server, including all volumes, system state, and application data, allowing you to restore a completely broken machine to new hardware or to a new virtual disk. This guide explains how to configure both types of backups using Windows Server Backup and how to perform a recovery.

Windows Server Backup is a built-in feature available at no additional cost. It does not require third-party software and integrates tightly with the Windows Recovery Environment. Before beginning, ensure you have a dedicated backup destination: an external USB drive, a mapped network share on a separate server, or a dedicated internal disk that is not part of the volume being backed up.

Step 1: Install Windows Server Backup

Open an elevated PowerShell window and install the Windows Server Backup feature:

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

After installation completes, open the Windows Server Backup console from Server Manager under Tools, or launch it by running wbadmin from a command prompt.

Step 2: Perform a Manual System State Backup

A System State backup captures critical OS components without requiring a full disk image. Run the following command from an elevated command prompt to back up the system state to a network share:

wbadmin start systemstatebackup -backupTarget:\BACKUPSERVERBackups -quiet

Replace \BACKUPSERVERBackups with the actual UNC path of your backup destination. The -quiet switch suppresses the confirmation prompt. System State backups for a typical Windows Server 2016 installation range from 10 GB to 30 GB depending on installed roles. The backup includes the registry, Active Directory (if the server is a domain controller), SYSVOL, boot files, and the COM+ class registration database.

Step 3: Perform a Bare Metal Recovery Backup

A Bare Metal Recovery backup is a superset of the System State backup. It captures all critical volumes required to restore the server from scratch. Run the following command to create a bare metal backup to a local disk:

wbadmin start backup -backupTarget:E: -include:C: -allCritical -systemState -vssFull -quiet

The -allCritical flag automatically includes all volumes that contain operating system components, not just the C: drive. The -vssFull parameter instructs the Volume Shadow Copy Service to create a full VSS snapshot rather than a copy-only snapshot, which enables differential or incremental chaining in subsequent backups. Replace E: with the drive letter of your backup destination.

Step 4: Schedule Automated Backups via GUI

Open the Windows Server Backup console and click Backup Schedule in the Actions pane. The Backup Schedule Wizard launches. Select Custom to control which volumes are included. Add all critical volumes and enable the System State option. Choose the schedule frequency, such as daily at 2:00 AM. For the backup destination, select Back up to a shared network folder if you are targeting a UNC path, or select Back up to a volume for a dedicated local disk. Complete the wizard to register the scheduled task.

Step 5: Verify Backup Integrity

After each backup completes, verify that it was recorded successfully using the following command:

wbadmin get versions

This command lists all available backup versions with their dates, backup targets, and the items included in each backup. Review the output to confirm that both SystemState and BareMetalRecovery are listed under the most recent backup version. You should automate this check by parsing the output in a scheduled PowerShell script that sends an alert email if no successful backup is found within the last 24 hours.

Step 6: Recover System State

To restore the system state on a running server, for example to roll back a failed Group Policy change or a corrupted registry hive, boot into Directory Services Restore Mode if the server is a domain controller, or simply run the following from an elevated command prompt on a non-domain controller:

wbadmin start systemstaterecovery -version:MM/DD/YYYY-HH:MM -backupTarget:\BACKUPSERVERBackups -quiet

Replace the version timestamp with the exact value shown in the wbadmin get versions output. The server will perform the restoration and then require a reboot to apply the recovered state.

Step 7: Perform a Bare Metal Recovery

If the server hardware fails entirely or the OS disk is corrupted beyond repair, boot the replacement server from a Windows Server 2016 installation DVD or USB media. On the initial setup screen, choose Repair your computer rather than installing Windows. Navigate to Troubleshoot, then System Image Recovery. Windows RE will detect available backup sets on network shares or locally attached disks. Select the most recent bare metal backup version, confirm the disk layout options, and start the recovery. The process will restore the OS, all drivers, installed applications, and data volumes to the state captured at the time of the backup.

Step 8: Test Recovery Regularly

A backup that has never been tested is a backup of unknown value. Schedule quarterly bare metal recovery tests using a virtual machine on Hyper-V. Attach the backup destination as a data disk to a new VM, boot from installation media, and perform the recovery. Verify that the recovered OS boots successfully, that key services start, and that applications function correctly. Document the time required to complete recovery so that you can accurately report Recovery Time Objectives to stakeholders.

Combining System State and Bare Metal Recovery backups, with automated scheduling, integrity verification, and regular recovery testing, gives you a comprehensive protection strategy for Windows Server 2016 that meets the requirements of most regulatory compliance frameworks.