How to Set Up Windows Server Backup on Windows Server 2016

Windows Server Backup is a built-in feature of Windows Server 2016 that allows administrators to protect critical data and system configurations without purchasing third-party software. It supports full server backups, bare metal recovery, individual volume and folder backups, and scheduled automatic backup jobs. Setting it up correctly ensures that your organization can recover quickly from hardware failures, ransomware attacks, accidental deletions, and other disasters.

This tutorial walks through installing the Windows Server Backup feature, configuring scheduled backups, performing manual backups, and verifying backup integrity on Windows Server 2016.

Step 1: Install the Windows Server Backup Feature

Windows Server Backup is not installed by default. You must add it through Server Manager or PowerShell.

To install via PowerShell, open an elevated PowerShell prompt and run:

Install-WindowsFeature Windows-Server-Backup

To install via Server Manager, open Server Manager, click Manage, then Add Roles and Features. Proceed through the wizard until you reach Features, then check Windows Server Backup and complete the installation.

After installation, verify the feature is present:

Get-WindowsFeature Windows-Server-Backup

Step 2: Open the Windows Server Backup Console

Launch Windows Server Backup from the Start menu or from Server Manager under Tools. The console displays backup status, scheduled jobs, and recovery options.

Alternatively, access it from PowerShell:

wbadmin /?

The wbadmin command-line tool is the primary interface for scripted backup operations and is equivalent in capability to the GUI console.

Step 3: Configure a Backup Schedule

In the Windows Server Backup console, click Backup Schedule in the right-hand Actions panel. The Backup Schedule Wizard opens. Choose between Full Server backup (recommended for bare metal recovery) or Custom backup (specific volumes or folders).

Select backup frequency—once or multiple times daily. Then specify a destination: a dedicated disk, a volume, or a network share. Microsoft recommends a dedicated backup disk because it protects against the same hardware failure that could affect the data disk.

To configure a scheduled backup via PowerShell:

$policy = New-WBPolicy
$fileSpec = New-WBFileSpec -FileSpec "C:"
Add-WBVolume -Policy $policy -Volume (Get-WBVolume -AllVolumes | Where-Object { $_.MountPath -eq "C:" })
$backupTarget = New-WBBackupTarget -VolumePath "D:"
Add-WBBackupTarget -Policy $policy -Target $backupTarget
Set-WBSchedule -Policy $policy -Schedule 23:00
Set-WBPolicy -Policy $policy

This example schedules a nightly backup of the C: volume to D: at 11:00 PM.

Step 4: Perform a Manual Backup

To run a one-time backup immediately from the console, click Backup Once in the Actions panel and follow the wizard. To perform the same operation from the command line:

wbadmin start backup -backupTarget:D: -include:C: -allCritical -quiet

The -allCritical flag ensures all critical volumes required for system recovery are included. The -quiet flag suppresses confirmation prompts, which is useful in scripts.

Step 5: Back Up to a Network Share

Backing up to a UNC network path is supported but stored as a single backup copy (not versioned like disk targets). Use the following command:

wbadmin start backup -backupTarget:\fileserverbackups -include:C: -allCritical -user:DOMAINBackupAdmin -password:YourPassword -quiet

Ensure the backup account has write permissions to the share. Network backups are useful when local storage is limited or when an offsite copy is required.

Step 6: Verify Backup Status

After a backup completes, review its status to confirm it succeeded:

wbadmin get status

To list all available backup versions:

wbadmin get versions

Check the Windows Event Log for backup-related events under Applications and Services Logs > Microsoft > Windows > Backup.

Step 7: Test Recovery

A backup is only useful if recovery works. Test file-level recovery by opening the console, clicking Recover, and walking through the Recovery Wizard to restore a test file from a recent backup version.

For command-line recovery of a specific file:

wbadmin start recovery -version:05/17/2026-23:00 -itemType:File -items:C:ImportantFoldertestfile.txt -recoveryTarget:C:Restored -quiet

Step 8: Bare Metal Recovery Preparation

To prepare for bare metal recovery, ensure System State and all critical volumes are included in the backup. Create a Windows Recovery Environment (WinRE) bootable USB or DVD from the Windows Server 2016 installation media. During disaster recovery, boot from the media, select Repair your computer, and use the backup created by Windows Server Backup to restore the entire server.

Best Practices

Store backups on a separate physical disk or an offsite network share to protect against localized failures. Test recovery procedures quarterly to validate backup integrity. Monitor backup job results daily through Event Viewer or email notifications configured via Task Scheduler. Retain multiple backup generations to allow rollback beyond the most recent infection or corruption event. Consider complementing Windows Server Backup with Azure Backup for cloud-based, long-term retention.

Windows Server Backup is a reliable, zero-cost first layer of data protection. Combining it with disciplined scheduling, offsite storage, and regular recovery testing creates a resilient backup strategy for Windows Server 2016 environments.