Windows Server Backup: Backup, Restore, wbadmin & Bare Metal Recovery

Windows Server Backup is the built-in Windows Server feature for creating file, volume, System State, and full-server backups, and for restoring them. wbadmin is its command-line interface. A completed job does not prove the backup is usable: you still need the right target, the right volumes, verified versions and contents, and a tested restore path. This guide covers the native lifecycle in order – install, back up, verify, restore files or volumes, and recover the whole server with Bare Metal Recovery.

What Is Windows Server Backup?

Windows Server Backup is a Windows Server feature (not a role) that provides file/folder, volume, System State, and full-server backup and recovery, coordinated through VSS. You manage it through its own console, the wbadmin command-line tool, or the WindowsServerBackup PowerShell module.

A “full server” or BMR-capable backup does not automatically mean every volume on the machine. It means the volumes selected for that job, and -allCritical specifically means the volumes required for OS recovery. The backup itself also isn’t bootable media; Bare Metal Recovery starts from Windows Setup, WinRE, or Windows PE, which then reads the backup image.

Windows Server Backup isn’t continuous data protection or an agent-based VM backup platform. It coordinates with VSS writers, but application-level recovery depends on the workload and whether that application registers its own recovery components. Treat database- or mailbox-level recovery as an application-specific procedure. For a standalone server or a single-role SMB box, the native tool covers the practical scenarios: deleted files, a failed update, OS corruption, or a replaced system disk.

Install Windows Server Backup

Verify:

Or via Server Manager: Add Roles and Features > Features > Windows Server Backup. Run wbadmin from an elevated prompt with an account in Backup Operators or Administrators.

Choose a Windows Server Backup Target

The target affects version management, retention, and how well the backup is isolated from a failure on the source server.

Windows Server Backup to a Network Share

A UNC path is supported, but backing up the same computer to the same shared-folder target repeatedly overwrites the previous backup at that target. If the new backup fails after the old one has already been overwritten, you can end up with no usable backup at all.

Preserve multiple restore points through an external retention design: separate subfolders, NAS snapshots, or an independently managed rotation. The feature does not keep native multi-version retention on a share the way it does on a dedicated local disk. wbadmin enable backup also supports only one shared-folder target at a time.

Verify what actually exists at the target rather than trusting the job status:

If you expect several restore points and only one appears, the retention design is not preserving multiple copies, even if every job reports Success.

Create Windows Server Backups with wbadmin

Create a One-Time Backup

-backupTarget is the destination. -allCritical includes the volumes required for OS and BMR recovery; use -include: for anything beyond that. -vssFull affects VSS backup history and application transaction logs. It is not just an “application-consistent” switch. On a server protected by another backup product, it can also affect that product’s log-truncation behavior.

Back Up Additional Data Volumes

The target must be separate from the protected volumes: here D: and E: are data volumes, and F: stores the backup. Confirm the volumes made it in with wbadmin get items rather than assuming -allCritical covered them.

Schedule a Backup

Use -addtarget, not -backupTarget, for a scheduled job. Microsoft documents -addtarget as accepting a UNC path to a remote shared folder, with -user and -password supplying the share credentials; the account must be a member of Administrators or Backup Operators on the server being backed up. Use a dedicated backup service account with permission to the remote target, and keep its password out of tickets, screenshots, and plaintext scripts. The schedule lands in Task Scheduler under \Microsoft\Windows\Backup.

The distinction matters: start backup runs once, while enable backup creates the recurring job. A one-time backup taken before a change is not a backup policy.

Verify a Windows Server Backup

A backup is not proven until you verify its versions, contents, and at least one restore path.

Check the Current Job

This reports the currently running backup or recovery operation, not a history of completed jobs. Use it while something is actively running.

Check Previous Job History

This retrieves previous backup or recovery job objects with their timing, state, and error details. Reviewing several runs makes recurring warnings easier to spot, including problems that do not stop a job from completing.

List Available Backup Versions

Shows backup time, target, version identifier, and recoverable items for each version. An empty result does not automatically mean the job failed: a wrong -machine value or target path can produce the same empty-looking output. Check those first.

Verify Backup Contents

For a remote backup, add -backupTarget and -machine. Use this to confirm a specific data volume (D:, E:, or an application volume) is present in the selected version before you need to restore it.

Restore Files and Folders from Windows Server Backup

File-level recovery runs from the live OS, so no recovery media is required.

GUI: Windows Server Backup > Recover > This server (or A backup stored on another location) > select the version > Files and folders > browse to the items > choose original or alternate location.

Command line:

Take the version identifier from wbadmin get versions. Restoring to an alternate path such as D:\Recovered lets you compare the recovered data before replacing the original.

To restore from a network share, add -backupTarget and -machine. Microsoft requires -machine whenever -backupTarget is specified.

Restore a Volume from Windows Server Backup

Volume recovery restores an entire data volume from a selected backup version. Use the GUI recovery wizard (select Volumes instead of Files and folders) or wbadmin start recovery:

1. Identify the version with wbadmin get versions
2. Confirm the volume is in that version with wbadmin get items
3. Choose the target. Without -recoveryTarget, recovery goes to the original volume
4. Run the recovery. Microsoft documents a single volume per command for -itemType:Volume
5. Verify data and permissions on the restored volume before putting it back into service

Windows Server Backup Bare Metal Recovery

What Is Bare Metal Recovery?

Bare Metal Recovery (BMR) restores the operating system and critical volumes from a backup image when the server has no working OS, such as after a system disk replacement, unrecoverable OS corruption, or a rebuild onto replacement hardware. It runs from recovery media, not from inside Windows.

What a BMR-Capable Backup Must Include

-allCritical covers the volumes required for OS recovery: the system volume, boot volume, and volumes hosting system components. It is not automatically every volume on the server. Confirm with wbadmin get items that any additional volumes you need were actually included.

Before Starting Bare Metal Recovery

• The backup version is visible and accessible from the recovery environment
• Compatible Windows Server installation or recovery media is available for the server being recovered
• The target disk layout is verified: for recovery that preserves the original layout, Microsoft’s full-server recovery guidance calls for an equivalent number of disks, each the same size or larger than its source
• Storage or network drivers are available if the recovery environment can’t see the target disk or the backup source
• Network credentials are ready if restoring from a UNC path
• BitLocker or other volume-encryption requirements are accounted for

Bare Metal Recovery Procedure

1. Boot from Windows Server installation or recovery media for the server being recovered
2. Select Repair your computer, not Install
3. Open Troubleshoot
4. Select System Image Recovery
5. Choose the local or network backup location
6. Select the backup version
7. Review the disk and repartition options presented
8. Start the restore
9. Reboot and verify services, data volumes, and network configuration

Command-line bare metal recovery is also available through wbadmin start sysrecovery, which must be run from the Windows Recovery Environment rather than a running OS. For most recoveries, the GUI wizard covers the same operation.

If the restore completes but Windows doesn’t boot, that’s a separate problem from the restore itself – continue with Windows Server Boot Failure Recovery.

Bare Metal Recovery from a Network Share

When the backup image lives on a NAS or file server, the recovery environment needs network access before it can see the backup.

1. In the System Image Recovery wizard, choose Select a system image, then Advanced > Search for a system image on the network
2. Enter the UNC path, for example \\NAS\backups\SERVER01
3. Supply credentials for the share when prompted
4. Select the machine and version, then continue as in the standard procedure

If the share isn’t reachable, the recovery environment may lack a NIC driver; load it through the wizard’s driver option. Confirm volume assignments before relying on drive letters in the recovery environment – the system volume is not guaranteed to be C: there:

BMR to Different Hardware

Restoring to different storage or network hardware can require drivers that are not present in the image, which carries drivers from the original hardware. INACCESSIBLE_BOOT_DEVICE after an otherwise completed restore points to a storage or boot-driver gap, which is a boot-recovery problem at that point.

Prepare ahead of time by exporting drivers and keeping them alongside the backup:

If needed after BMR, inject drivers from WinRE against the correct offline Windows path. Confirm the drive letter with DiskPart first:

Driver injection can resolve some storage and NIC issues, but dissimilar-hardware restore is not guaranteed. Test the path in a lab or VM first – a successful test proves the backup is readable and the restore mechanism works, not that the image will boot on different physical hardware.

Windows Server Backup Troubleshooting

Backup Version Not Found

Check the target path, the -machine value if remote, catalog visibility, job history (Get-WBJob -Previous 5), and share availability before concluding the backup never ran.

Required Volume Missing

If wbadmin get items doesn’t list a needed volume, add it with -include: and reschedule. -allCritical alone won’t add it.

Network Share Backup Fails

Check the share path, credentials, share and NTFS permissions, connectivity, free space on the target, and the exact Microsoft-Windows-Backup error code. Whether the machine account or a specified user account connects depends on how the backup was configured – check rather than assume.

VSS / System Writer Failure

Capture the failed writer and exact backup error, identify the service that owns the writer, check its event log, correct the underlying issue, re-check the writer state, and then rerun the backup. A reboot is not a universal fix.

Event IDs do not identify a universal cause either. Microsoft’s Event ID 513 documentation covers a specific System Writer/CAPI2 scenario, and Microsoft-Windows-Backup Event 517 appears in more than one context, including a documented System Writer scenario. Record the accompanying error code instead of assuming one cause.

Domain Controller and System State Backup Boundary

Windows Server Backup can create a System State backup on a domain controller, but DC backup and restore have Active Directory-specific requirements beyond this page. Use Active Directory Backup with Windows Server Backup and wbadmin for System State creation, backup lifetime, and AD-aware verification, and Restore a Domain Controller from Backup for the actual restore procedure. For losing multiple DCs or the whole forest, see Active Directory Forest Recovery.

Hyper-V host and VM backup, checkpoints, and VM restore failures are covered in Hyper-V Backup: VSS, Checkpoints, and Restore Failures.

Windows Server Backup Verification Checklist

• wbadmin get versions shows at least one successful, expected version
• wbadmin get items -version:<VersionIdentifier> confirms all needed volumes are present, including anything beyond -allCritical
• Get-WBJob -Previous 5 shows consistent results with no unexplained recurring errors
• At least one file restore has actually completed
• BMR tested in a lab or VM at least once, understanding that this proves the backup and restore mechanism, not hardware compatibility
• A network-share target has a retention design beyond a single overwritten version
• vssadmin list writers shows no writers in a Failed state
• Backup account permissions confirmed at the share and NTFS layer

FAQ

What is Windows Server Backup?

Windows Server Backup is the built-in Windows Server feature for creating and restoring file/folder, volume, System State, and full-server backups through its console, wbadmin, or PowerShell.

What is wbadmin used for?

It is the command-line interface for Windows Server Backup, used to create one-time or scheduled backups, check job status and versions, verify contents, and run recovery without the GUI.

Does Windows Server Backup support network shares?

Yes, but backing up the same computer to the same shared-folder target repeatedly overwrites the previous backup there. Design retention explicitly with dated subfolders, NAS snapshots, or target rotation.

How do I verify a Windows Server Backup?

Check job history with Get-WBJob -Previous 5, confirm versions with wbadmin get versions, confirm contents with wbadmin get items, and periodically perform a real test restore. A completed job status alone doesn’t prove the backup is usable.

Does -allCritical back up every volume?

No. It covers the volumes required for OS and BMR recovery. Additional data volumes need -include:, and wbadmin get items confirms whether they made it in.

How do I restore files from Windows Server Backup?

Open Windows Server Backup > Recover, choose the version, select Files and folders, and restore to the original or an alternate location. From the command line, use wbadmin start recovery with -itemtype:file. Both run from the live OS without recovery media.

What is Windows Server Backup Bare Metal Recovery?

BMR restores the server’s operating system and critical volumes from a backup image when the original installation is unavailable or the system disk has been replaced. It runs from Windows Setup or recovery media, not from within a running OS.

Can Windows Server Backup restore to different hardware?

Sometimes. BMR to dissimilar hardware can work when the recovery environment and restored image have the right storage and network drivers, but it isn’t guaranteed. Export drivers in advance and test the path before relying on it.

Can Windows Server Backup back up Active Directory?

It can create a System State backup that includes AD on a domain controller, but DC backup and restore have their own requirements. See the dedicated Active Directory Backup and Restore a Domain Controller guides linked above.