How to Set Up Windows Server Backup on Windows Server 2025

Windows Server Backup is the built-in backup solution included with Windows Server 2025 at no additional cost. While third-party tools offer more advanced features, Windows Server Backup provides a reliable, native option for protecting critical data, system state, and entire server volumes. Whether you are running a small business file server or protecting a domain controller, understanding how to configure, schedule, monitor, and restore from Windows Server Backup is an essential skill for every Windows Server administrator. This guide walks you through the complete process from installation to bare metal recovery planning.

Prerequisites

Windows Server 2025 installed (Standard or Datacenter edition)
Administrator account or membership in the Backup Operators group
A backup destination: local disk (dedicated, not the OS volume), external USB drive, or a network share (UNC path)
Sufficient storage space — at minimum 1.5× the size of the data being backed up
PowerShell 5.1 or later (included with Windows Server 2025)
Network share credentials if backing up to a remote location

Step 1: Install the Windows Server Backup Feature

Windows Server Backup is not installed by default. You must add it as a Windows feature before using either the GUI or PowerShell cmdlets. Open an elevated PowerShell session and run the following command:

# Install Windows Server Backup feature and management tools
Install-WindowsFeature -Name Windows-Server-Backup -IncludeManagementTools

# Verify the feature installed successfully
Get-WindowsFeature -Name Windows-Server-Backup

After installation, the wbadmin command-line tool and the Windows Server Backup snap-in become available in Server Manager under Tools. You can also access backup cmdlets in PowerShell through the WindowsServerBackup module, which is loaded automatically once the feature is installed.

Step 2: Run an Ad-Hoc Backup with wbadmin

The quickest way to take a backup is with the wbadmin start backup command. This is useful for immediate one-time backups before maintenance windows or major changes. The following examples cover backing up all critical volumes to a local disk and to a network share:

# Backup all critical volumes to a local disk (disk must be pre-formatted and dedicated)
wbadmin start backup -backupTarget:E: -allCritical -quiet

# Backup all critical volumes to a network share
wbadmin start backup -backupTarget:\NAS01BackupsWS2025 -allCritical -user:DOMAINBackupUser -password:P@ssw0rd -quiet

# Backup specific volumes only (C: and D: in this example)
wbadmin start backup -backupTarget:E: -include:C:,D: -quiet

# Backup system state only (suitable for domain controllers)
wbadmin start backup -backupTarget:E: -systemState -quiet

The -allCritical flag automatically includes all volumes required for a complete system recovery, including the EFI partition, system reserved partition, and the OS volume. Always use this flag when protecting a server that may need bare metal recovery.

Step 3: Create a Scheduled Backup Policy with PowerShell

For ongoing protection, configure a backup policy that runs automatically on a schedule. The Windows Server Backup PowerShell module provides a set of WB* cmdlets for building and applying backup policies programmatically:

# Create a new backup policy object
$Policy = New-WBPolicy

# Add the C: volume to the backup scope
$Volume = Get-WBVolume -VolumePath "C:"
Add-WBVolume -Policy $Policy -Volume $Volume

# Add the D: volume as well
$VolumeD = Get-WBVolume -VolumePath "D:"
Add-WBVolume -Policy $Policy -Volume $VolumeD

# Include system state (required for AD DS domain controllers)
Add-WBSystemState -Policy $Policy

# Configure backup to run daily at 02:00 and 14:00
$Schedule = @([datetime]"02:00", [datetime]"14:00")
Set-WBSchedule -Policy $Policy -Schedule $Schedule

# Set a local disk as the backup target
# IMPORTANT: The target disk will be reformatted and dedicated to backup
$TargetDisk = Get-WBDisk | Where-Object { $_.DiskNumber -eq 1 }
$BackupTarget = New-WBBackupTarget -Disk $TargetDisk -Label "WS2025-Backup" -PreserveExistingBackups $false
Add-WBBackupTarget -Policy $Policy -Target $BackupTarget

# Alternatively, set a network share as the backup target
# $NetworkTarget = New-WBBackupTarget -NetworkPath "\NAS01BackupsWS2025" -Credential (Get-Credential)
# Add-WBBackupTarget -Policy $Policy -Target $NetworkTarget

# Configure VSS backup options (Full creates VSS full backup, Copy does not truncate logs)
Set-WBVssBackupOptions -Policy $Policy -VssCopyBackup
# For Exchange or SQL with log truncation, use:
# Set-WBVssBackupOptions -Policy $Policy -VssFullBackup

# Apply the policy to make it active
Set-WBPolicy -Policy $Policy -Force

# Verify the policy is configured correctly
Get-WBPolicy

Step 4: Monitor Backup Jobs and Summary

After backups have run, use the following cmdlets to check backup status, review job history, and confirm that backups completed without errors:

# View the overall backup summary (last backup time, result, next scheduled backup)
Get-WBSummary

# View currently running backup jobs
Get-WBJob

# List all available backup versions (useful before a restore)
wbadmin get versions

# List versions with detailed information including backup target location
wbadmin get versions -backupTarget:E:

# Get the backup catalog from a network share
wbadmin get versions -backupTarget:\NAS01BackupsWS2025 -machine:WS2025-SRV01

The Get-WBSummary output shows the last backup time, whether it succeeded or failed, how long it took, and when the next scheduled backup is due. Integrate this into a monitoring script or scheduled task to send alerts if the last backup is older than expected.

Step 5: Restore Files and Folders

Windows Server Backup supports granular file-level recovery without requiring a full system restore. Use wbadmin start recovery to restore specific files or folders from any available backup version:

# List files in a specific backup version to find what you need
wbadmin get items -version:05/17/2026-02:00 -backupTarget:E:

# Restore a specific folder to its original location
wbadmin start recovery `
    -version:05/17/2026-02:00 `
    -itemType:File `
    -items:"D:DataReports" `
    -recoveryTarget:"D:DataReports" `
    -overwrite:Overwrite `
    -quiet

# Restore a full volume
wbadmin start recovery `
    -version:05/17/2026-02:00 `
    -itemType:Volume `
    -items:D: `
    -recoveryTarget:D: `
    -quiet

# Restore system state (Active Directory, registry, SYSVOL)
wbadmin start systemstaterecovery -version:05/17/2026-02:00 -quiet

Step 6: Bare Metal Recovery with Windows Recovery Environment

If your server experiences a catastrophic failure — corrupt OS, failed system disk, or hardware replacement — you can perform a bare metal recovery by booting from Windows Server 2025 installation media and using the built-in recovery tools:

Boot the server from Windows Server 2025 DVD or USB installation media.
On the first screen, click Next, then choose Repair your computer.
Navigate to Troubleshoot → System Image Recovery.
Windows will automatically search for backup images on attached disks. If the backup is on a network share, select Select a system image and enter the UNC path and credentials.
Choose the backup version to restore and confirm the target disk.
Wait for the restore to complete — the server will reboot automatically.

For scripted bare metal recovery scenarios (e.g., replacing hardware), ensure the target server can reach the network share by pre-loading network drivers in WinRE. Windows Server 2025 includes updated WinRE with improved hardware driver support.

Step 7: Verify Backup Integrity

Never assume a backup is valid until you have verified it. Use the catalog validation and manual inspection to confirm your backups are restorable:

# Validate the backup catalog on a local disk
wbadmin get catalog -backupTarget:E:

# Validate the backup catalog on a network share
wbadmin get catalog -backupTarget:\NAS01BackupsWS2025 -machine:WS2025-SRV01

# Check the backup health and catalog status through the policy
Get-WBBackupSet

# Delete the oldest backup version manually if disk space is low
wbadmin delete catalog -quiet
# Note: deleting the catalog does not delete backup data, only the index

# List and confirm backup versions before deletion
wbadmin get versions -backupTarget:E:

Best practice is to perform a test restore of at least one file or folder monthly. For system state backups protecting domain controllers, schedule a quarterly full bare metal recovery test in a lab environment to validate the entire restore chain.

Conclusion

Windows Server Backup on Windows Server 2025 provides a capable, zero-cost backup foundation that every Windows Server administrator should have configured and tested. By installing the feature, building a scheduled policy with PowerShell, monitoring job outcomes with Get-WBSummary, and regularly validating restores, you establish a baseline data protection posture without requiring additional software licensing. For environments with more complex requirements — long-term retention, application-aware backups for SQL Server or Exchange, or cloud-integrated storage — consider layering Azure Backup or a third-party solution on top of this native capability. The most important principle remains constant: a backup you have never tested is not a backup you can rely on.

Links

Newsletter

Contact