Windows Server includes a free backup tool that can protect files, applications and the whole system. Windows Server Backup and its command-line tool wbadmin are enough for many single-server setups when combined with an off-site copy.
Before you start
- RDP access as an administrator.
- A backup target that is not the system disk: a second virtual disk, or a network share (SMB) on another server.
- Enough space: plan for roughly the used size of the volumes you back up, plus room for several versions.
Install Windows Server Backup
In PowerShell as administrator:
Install-WindowsFeature Windows-Server-BackupOpen the GUI with wbadmin.msc.
Choose what to back up
| Option | Covers | Use for |
|---|---|---|
| Full server | All volumes, system state, bare metal recovery | Complete recovery after disaster |
| Bare metal recovery | Everything needed to rebuild the OS | Restoring to new hardware or a new VPS |
| System state | Registry, boot files, Active Directory, IIS config | Configuration recovery |
| Custom folders | Selected data folders | Websites, databases dumps, app data |
Schedule a daily backup (GUI)
- In Windows Server Backup, click Backup Schedule in the Actions pane.
- Choose Full server or Custom and select items.
- Pick Once a day and a quiet time, e.g. 03:00.
- Choose the destination: a dedicated disk (it will be formatted and hidden) or a network share.
- Confirm and finish.
Note: a network share keeps only the latest backup, each run overwrites the previous one. A dedicated disk keeps multiple versions automatically until space runs out.
Schedule a backup with wbadmin
Daily bare metal and system state backup of C: to disk E: at 03:00:
wbadmin enable backup -addtarget:E: -include:C: -allCritical -systemState -schedule:03:00 -quietRun a one-off backup to a network share:
wbadmin start backup -backupTarget:\\10.0.0.20\backups -include:C:,D: -allCritical -vssFull -quietList existing backups:
wbadmin get versionsBack up databases correctly
Windows Server Backup uses VSS snapshots, which SQL Server supports. For other databases (MySQL, MariaDB), schedule a dump to a data folder before the backup runs, so the backup always contains a consistent export.
Restore files and folders
- Open Windows Server Backup and click Recover.
- Choose the backup location and the date.
- Select Files and folders, browse to the items and choose to restore to the original or another location.
From the command line:
wbadmin start recovery -version:01/15/2025-03:00 -itemType:File -items:D:\Sites\example.com -recoveryTarget:D:\Restore -recursiveUse the exact version string from wbadmin get versions.
Full server recovery
To restore the whole system, boot the VPS from Windows Server installation media (ask support to mount the ISO), choose Repair your computer → Troubleshoot → System Image Recovery, and select the backup. The backup disk or share must be reachable from the recovery environment.
Keep a copy off the server
A backup on the same VPS does not survive the VPS being lost or encrypted by ransomware. Copy backups to another location regularly, for example with Robocopy to a remote share or a cloud storage tool, and follow the 3-2-1 rule.
Troubleshooting
- The backup storage location is not available: check the share permissions and that the backup runs with credentials that can write to it.
- VSS errors (event IDs in Application log): run
vssadmin list writers; restart the service whose writer is failed. - Not enough space: exclude temporary folders or use a larger target disk.
- Scheduled backup did not run: check Event Viewer under Applications and Services Logs → Microsoft → Windows → Backup.
Windows Server Backup FAQ
Is Windows Server Backup free?
Yes, it is included with Windows Server at no extra cost.
Does it support incremental backups?
Yes, backups to a dedicated disk are block-level incremental after the first full backup.
Should I still use provider snapshots?
Snapshots are a useful extra layer for quick rollbacks, but an independent backup stored elsewhere is still important.