Windows Server Backup is a built-in feature of Windows Server that can back up volumes, system state, and bare metal recovery data to a local drive, network share, or removable storage. It is not the most feature-rich backup solution, but it is free, integrated, and reliable for basic server protection. Here is how to set it up.
Install Windows Server Backup
Windows Server Backup is not installed by default. Add it as a feature:
- Open Server Manager → Manage → Add Roles and Features
- Click through to the Features page
- Tick Windows Server Backup
- Click Install
Or via PowerShell:
Install-WindowsFeature Windows-Server-BackupOpen Windows Server Backup
After installation, find it in Server Manager → Tools → Windows Server Backup, or search for “wbadmin” in Start.
Configure a Scheduled Backup
- In the Windows Server Backup console, click Backup Schedule in the right-hand Actions panel
- Choose Full server (backs up everything including system state and all volumes) or Custom (select specific volumes or folders)
- Set the backup time — once daily is the minimum for most servers; critical servers should back up at least twice daily
- Choose the destination:
- Dedicated disk: a local drive dedicated solely to backups — Windows formats it and manages rotation automatically. The drive will not appear in File Explorer after configuration — this is by design.
- Volume: a drive letter on an existing disk — less reliable than a dedicated disk but works for testing
- Remote shared folder: a UNC path to a network share — backups go over the network to a NAS or another server
- Click Finish — the backup schedule is created and will run automatically
Run a Backup Immediately
To take a backup now without waiting for the scheduled time:
- Click Backup Once in the Actions panel
- Choose Scheduled backup options (uses the same settings as the scheduled job) or Different options to customise
- Click Backup
Via command line:
# Back up all volumes to a network share
wbadmin start backup -backupTarget:\\NAS\ServerBackups -allCritical -systemState -vssFull -quietVerify the Backup
After a backup completes, verify it ran successfully:
- In the Windows Server Backup console, check the Messages panel for the last backup status
- Check Event Viewer → Applications and Services Logs → Microsoft → Windows → Backup for backup events
- Via PowerShell:
wbadmin get statusduring a backup, orwbadmin get versionsto list available backup versions
Do not assume a backup is working — check it. A backup that silently fails is the same as no backup at all.
What Windows Server Backup Protects
- System state: Active Directory, registry, boot files, and COM+ database — essential for recovering a domain controller
- Bare metal recovery: a full server restore from scratch onto the same or replacement hardware
- Volumes: complete volume backup for file and application recovery
Windows Server Backup does not back up at the file level with granular scheduling — it is a block-level volume backup. For individual file recovery, use shadow copies (Previous Versions) or a dedicated backup solution.
Limitations to Be Aware Of
- Only one scheduled backup destination — no rotation between multiple locations from the built-in tool
- No built-in encryption of backup data — anyone with access to the backup destination can read the files
- Does not support tape or cloud destinations natively
- No email notifications on failure without scripting (unlike commercial backup tools)
For production environments with multiple servers, consider a dedicated backup solution (Veeam Backup & Replication, Acronis, or Windows Azure Backup) that provides encryption, centralised management, email alerting, and cloud offsite capability.
Restoring from a Windows Server Backup
To recover files or folders:
- Open Windows Server Backup → Recover
- Select the backup version and browse to the file or folder
- Choose the recovery destination
For a full bare metal recovery, boot from Windows Server installation media → Repair your computer → System Image Recovery, then point to the backup location.
