Windows Server Backup and Recovery: A Complete Setup Guide

Overview

Windows backup is something most people configure once, forget about, and then desperately Google when disaster strikes. Whether you’re running a Windows Server 2019 or 2022 VPS, a Dedicated Server, or a self-managed instance, having a tested, reliable backup strategy isn’t optional — it’s the difference between a bad afternoon and a catastrophic data loss event.

Windows Server Backup (WSB) is Microsoft’s built-in solution. It handles full server backups, volume-level backups, system state backups, and bare-metal recovery images. It’s not the flashiest tool, but it’s well-integrated with the OS and doesn’t require a third-party agent. The command-line counterpart, wbadmin, gives you everything you need to automate and script backup jobs.

This article covers installation, scheduling automated backups, restoring files and full system images, and the problems you’re most likely to hit along the way. If you’ve inherited a server and aren’t sure whether backups are even running, start from the top.

Prerequisites

• Windows Server 2016, 2019, or 2022 (steps are consistent across all three; any differences are noted)
• Administrator or local administrator account on the server
• A backup destination: a separate local volume, external drive, network share (UNC path), or a mapped drive — not the same volume you’re backing up
• Sufficient free space on the backup destination — at minimum 1.5x the size of the data you’re protecting
• RDP access or physical/console access to the server
• For bare-metal recovery: Windows Server installation media (ISO or USB) matching your server’s OS version

Step 1: Install Windows Server Backup

WSB isn’t installed by default on most Server Core or minimal installs. Check first, then install if it’s missing.

Open PowerShell as Administrator and run:

Get-WindowsFeature -Name Windows-Server-Backup
Install-WindowsFeature -Name Windows-Server-Backup

If you prefer Server Manager: go to Manage > Add Roles and Features > Features, check Windows Server Backup, and click Install.

📝 Note: On Server Core installations, Server Manager isn’t available. Use the PowerShell method above.

Step 2: Configure a One-Time Backup via GUI

This is useful for an immediate pre-maintenance backup or to verify your setup works before automating it.

1. Open Windows Server Backup from the Start menu or via wbadmin start backup.
2. In the Actions pane on the right, click Backup Once.
3. Select Different options, then click Next.
4. Choose Full server to back up all volumes, or Custom to select specific volumes or folders.
5. Set your backup destination: local drive, remote shared folder, or DVD. For production use, choose a Remote shared folder (UNC path like \backupservershare) or a dedicated local volume.
6. Click Backup to start immediately.

⚠ Warning: Never back up to the same volume that contains your OS or the data you’re protecting. If that volume fails, you lose the backup too. Use a separate disk or a network share.

Step 3: Schedule Automated Backups via GUI

1. In Windows Server Backup, click Backup Schedule in the Actions pane.
2. Select Full server or Custom for the backup configuration.
3. Set the schedule — once or twice daily is typical for production servers. More frequent backups mean smaller recovery point objectives (RPO).
4. Choose your destination. If using a dedicated backup disk, WSB will format it and manage it automatically. If using a network share, you’ll provide a UNC path and credentials.
5. Click Finish to save the schedule.

📝 Note: When you select a local disk as a scheduled backup destination, WSB takes exclusive ownership of that disk and hides it from Windows Explorer. This is by design. Don’t panic when it disappears from This PC.

Step 4: Schedule and Run Backups via wbadmin (Command Line)

For scripting, automation, or Server Core environments, wbadmin is the right tool. Here’s how to run a full backup to a network share:

wbadmin start backup 
  -backupTarget:\backupserverwinbackups 
  -include:C:,D: 
  -allCritical 
  -systemState 
  -vssFull 
  -quiet

Breaking down the flags:

• -allCritical — includes all volumes required for a bare-metal recovery, even if you didn’t explicitly list them
• -systemState — backs up Active Directory, registry, COM+ class registration database, and boot files; essential if you’re running AD DS or DNS roles
• -vssFull — triggers a full VSS (Volume Shadow Copy) backup, which truncates transaction logs on supported apps like SQL Server; use -vssCopy if you have a separate SQL backup job handling log truncation
• -quiet — suppresses confirmation prompts, required for scripted/scheduled runs

To schedule this as a daily task via Task Scheduler:

schtasks /create /tn "DailyServerBackup" /tr "wbadmin start backup -backupTarget:\\backupserver\winbackups -allCritical -systemState -vssFull -quiet" /sc daily /st 02:00 /ru SYSTEM /f

📝 Note: The scheduled task runs as SYSTEM, which means the network share must allow the computer account (e.g., SERVERNAME$) write access, or you’ll need to specify alternate credentials using /ru and /rp flags.

Step 5: Restore Individual Files and Folders

This is the most common recovery scenario — someone deleted a file or a folder was corrupted.

1. Open Windows Server Backup and click Recover in the Actions pane.
2. Select where the backup is stored: This server or Another location (network or external drive).
3. Choose the backup date and time from the calendar.
4. Select Files and folders as the recovery type.
5. Browse to the file or folder you need and click Next.
6. Choose whether to restore to the original location or an alternate path. If you’re unsure, restore to an alternate path first and verify the file before overwriting anything live.
7. Click Recover.

Via command line:

wbadmin start recovery 
  -version:03/15/2025-02:00 
  -itemType:File 
  -items:C:UsersAdministratorDocumentsreport.xlsx 
  -recoveryTarget:C:Restored 
  -quiet

Get the correct version identifier first:

wbadmin get versions

Step 6: Bare-Metal Recovery (Full Server Restore)

This is the procedure when the server OS is unbootable or the system drive has failed. You need your Windows Server installation media and a backup that includes -allCritical.

1. Boot from the Windows Server ISO or USB.
2. On the language selection screen, click Next, then Repair your computer (bottom-left, not Install Now).
3. Click Troubleshoot > System Image Recovery.
4. Windows will scan for available backups. If it doesn’t find yours automatically, click Select a system image and provide the network share path or connect the external drive.
5. Select the backup version you want to restore, confirm the disk selection, and click through to start the recovery.

⚠ Warning: Bare-metal recovery will overwrite the entire target disk. Double-check you’ve selected the correct destination disk before confirming. On servers with multiple drives, it’s easy to select the wrong one.

Common Issues and Troubleshooting

Error 0x807800C5: The backup storage location is not valid

This usually means the backup destination is the same volume as the source, or WSB doesn’t have write access to the network share. Verify the destination is a different volume or UNC path. If it’s a network share, confirm the computer account has write permissions, not just the user account.

VSS Error: Volume Shadow Copy Service error — Unexpected error calling routine

VSS errors are annoyingly common and the event log messages are rarely helpful. The most frequent cause is a corrupted VSS provider or a third-party application holding VSS locks (antivirus software is a frequent offender). Start here:

vssadmin list writers
net stop vss
net stop swprv
net start swprv
net start vss

If writers show a Failed state, re-registering the VSS DLLs often resolves it. Search Microsoft’s KB for the specific writer name that’s failing — each application (SQL, Exchange, Hyper-V) has its own fix.

Backup Job Runs But No Files Are Created

Check the Windows Server Backup event log under Applications and Services Logs > Microsoft > Windows > Backup. The backup may have completed with warnings rather than errors, and the output location may have been redirected. Also confirm Task Scheduler actually fired the job — look under Task Scheduler Library for the last run time and result code.

“The system cannot find the path specified” During Recovery

This happens when the backup catalog is corrupted or the version identifier passed to wbadmin doesn’t match an available backup. Run wbadmin get versions to confirm the exact version string, and check whether the backup catalog needs rebuilding:

wbadmin delete catalog -quiet
wbadmin get versions -backupTarget:\backupserverwinbackups

📝 Note: Deleting the catalog only removes the local index. Your actual backup data on the destination is not affected.

Scheduled Backup Stops Running After a Password Change

If the scheduled task runs under a user account and that account’s password changed, the task will silently fail. Update the stored credentials in Task Scheduler, or switch the task to run as SYSTEM with proper share permissions configured on the network side.

Additional Recommendations

In my experience, the most common backup failure isn’t a technical one — it’s a backup that was set up correctly and then never verified. Schedule a monthly test restore to a non-production path and confirm the files are readable. A backup job that logs “Success” but produces unusable data is worse than no backup at all, because it gives false confidence.

If you’re running a Host & Tech Dedicated Server with Windows, I’d recommend storing backups off-server entirely — either to a network share on a separate system or to a cloud storage target mounted as a network drive. Local-only backups don’t protect you against disk controller failures or ransomware, both of which are real risks on production machines.

For critical workloads, pair WSB with application-level backups. SQL Server has its own backup system; don’t rely solely on VSS to catch it. Same applies to IIS configuration — export your IIS config separately using appcmd or the IIS Manager export feature.