Introduction to Windows Server Backup on Windows Server 2019

Windows Server Backup (WSB) is a built-in feature of Windows Server 2019 that provides reliable, block-level backup and recovery for your server. It supports full server backups, system state backups, bare metal recovery backups, and volume-level backups. Unlike third-party solutions, WSB integrates directly with the Volume Shadow Copy Service (VSS) to create consistent snapshots without requiring the server to be taken offline. This guide covers every step from installing the feature to scheduling automated backups and performing a recovery.

Installing the Windows Server Backup Feature

Windows Server Backup is not installed by default on Windows Server 2019. You must add it as a Windows feature using either Server Manager or PowerShell. The PowerShell method is recommended for automation and remote administration.

Open an elevated PowerShell session and run the following command to install Windows Server Backup and its associated command-line tools:

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

After the installation completes, verify the feature is installed:

Get-WindowsFeature -Name Windows-Server-Backup

You should see the Install State listed as Installed. The feature installs both the graphical snap-in (wbadmin.msc) and the wbadmin command-line utility.

Understanding Backup Types and Storage Destinations

Windows Server Backup supports several backup types. A full server backup captures all volumes on the server including the system state, applications, and data. A custom backup lets you select specific volumes or folders. A system state backup captures the registry, Active Directory (if installed), SYSVOL, IIS metabase, and boot files. Bare metal recovery (BMR) backups include everything needed to restore a server to new hardware.

Backup storage can be directed to a local volume, an external USB drive, a network share (UNC path), or an optical disc. Dedicated backup disks are strongly recommended because WSB can manage disk space rotation automatically when a dedicated disk is used. Network shares require credentials and have some limitations on backup scheduling.

Configuring a Backup Schedule via PowerShell

The wbadmin command-line tool is the primary interface for scripting and automating Windows Server Backup. The following example configures a nightly backup of the entire server to a dedicated backup disk. First, identify the disk ID of the destination disk:

wbadmin get disks

Note the Disk Identifier value (a GUID) for the disk you intend to use as the backup target. Then run the following command to create a scheduled backup policy. Replace the disk identifier with your actual value:

wbadmin enable backup -addtarget:{00000000-0000-0000-0000-000000000000} -schedule:21:00 -allCritical -vssfull -quiet

The -allCritical flag includes all critical volumes (those required to boot and run the OS). The -vssfull flag instructs VSS to perform a full backup, clearing the VSS backup history. The -schedule:21:00 sets the backup to run at 9:00 PM daily. You can specify multiple times separated by commas, for example -schedule:06:00,21:00 for twice-daily backups.

Performing a Manual Backup via Command Line

To run an immediate backup without waiting for the schedule, use the wbadmin start backup command. The following example backs up all critical volumes to a network share:

wbadmin start backup -backupTarget:\fileserver01backups -user:DOMAINbackupuser -password:P@ssw0rd -allCritical -vssfull -quiet

To back up a specific volume (for example, the D: drive) to a local disk:

wbadmin start backup -backupTarget:E: -include:D: -quiet

To perform a system state backup only, which is faster and sufficient for Active Directory recovery on a domain controller:

wbadmin start systemstatebackup -backupTarget:E: -quiet

Listing and Verifying Backup Versions

After backups run, you can list all available backup versions to verify they completed successfully:

wbadmin get versions

The output shows each backup version with its identifier, backup time, backup target, and what was backed up. To see details of a specific backup version, use its identifier:

wbadmin get versions -backupTarget:E: -machine:SERVER01

To list items within a specific backup version (to see which volumes and files are available for restore):

wbadmin get items -version:05/17/2026-21:00 -backupTarget:E:

Restoring Files and Folders from Backup

Windows Server Backup allows granular file and folder recovery without restoring the entire volume. To recover a specific file, first identify the backup version using wbadmin get versions, then run:

wbadmin start recovery -version:05/17/2026-21:00 -items:C:UsersAdminDocumentsreport.docx -itemtype:File -recoveryTarget:C:Restore -quiet

To restore an entire folder:

wbadmin start recovery -version:05/17/2026-21:00 -items:C:inetpubwwwroot -itemtype:File -recoveryTarget:C:Restore -quiet

To restore an entire volume (for example, restore D: from backup):

wbadmin start recovery -version:05/17/2026-21:00 -items:D: -itemtype:Volume -recoveryTarget:D: -quiet

Using the Windows Server Backup GUI Snap-in

The graphical interface provides a wizard-driven approach for configuring backup schedules and performing recoveries. Launch it from Server Manager by navigating to Tools > Windows Server Backup, or by running wbadmin.msc from the Run dialog.

In the left pane, select Local Backup. In the Actions pane on the right, you will find Backup Schedule to configure recurring backups and Backup Once for an immediate backup. The Recovery Wizard walks you through restoring volumes, folders, or the system state from any available backup version.

Checking Backup Status and Event Logs

Backup operation results are written to the Windows event log under Applications and Services Logs > Microsoft > Windows > Backup. Use PowerShell to query recent backup events:

Get-WinEvent -LogName "Microsoft-Windows-Backup" | Select-Object TimeCreated, LevelDisplayName, Message | Format-List

Event ID 4 indicates a successful backup. Event ID 5 indicates a failed backup. You can set up Task Scheduler to email an alert on failure by creating a task triggered by Event ID 5 in the Backup event log.

To check current backup policy settings configured on the server:

wbadmin get schedule

Removing Old Backup Versions

When backing up to a dedicated disk, Windows Server Backup manages disk space automatically and will overwrite the oldest backup when space is needed. For network share backups, you must manually manage old versions. To delete a specific backup version:

wbadmin delete backup -version:04/01/2026-21:00 -backupTarget:\fileserver01backups -machine:SERVER01 -quiet

To keep only the most recent backup and delete all others:

wbadmin delete backup -keepVersions:1 -quiet

Best Practices for Windows Server Backup

Always follow the 3-2-1 backup rule: maintain three copies of data, on two different storage media types, with one copy stored offsite. Windows Server Backup should be considered a first line of defense, complemented by a secondary solution such as Azure Backup or a third-party tool for offsite protection.

Test your backups regularly by performing recovery drills. A backup that has never been tested is an untested assumption. Schedule monthly recovery tests where you restore a volume or critical file to an alternate location and verify the content is intact and usable.

Store backup credentials securely. Avoid embedding plaintext passwords in scheduled tasks or scripts; instead, use Windows Credential Manager or a secrets management solution. Monitor backup event logs daily using a monitoring tool or Windows Admin Center to catch failures before they become a crisis.